[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#227005: marked as done (xfree86: build XDirectFB X server)



Your message dated Mon, 28 Feb 2011 00:00:49 +0100
with message-id <20110227230049.GA23357@debian.org>
and subject line Re: Bug#227005: xfree86: Patch to build XDirectFB server
has caused the Debian Bug report #227005,
regarding xfree86: build XDirectFB X server
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
227005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=227005
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xfree86
Severity: wishlist

I have also submitted a RFP item on wnpp for this: #225010, because this
patch makes a XDirectFB executable which is a different X server with
DirectFB as backend and should be in a seperate binary package, but be
generated from the same source package.

Info pasted from #225010:

<readme>
XDirectFB
---------
                                                                                                                                                      
                                                                                                                                                      
XDirectFB is a rootless X Server using DirectFB windows for
X11 toplevel windows. This way you can adjust the opacity
of every application with your mouse wheel (while holding
CapsLock or Meta down over a window). More details about
these shortcuts can be found in the DirectFB README.
                                                                                                                                                      
Window movements are initiated by the applications or
the window manager. The graphical movement is done by
DirectFB using available hardware acceleration.
                                                                                                                                                      
Overlapping toplevel windows do not cause expose events,
i.e. redrawing of the window contents, as they are DirectFB
windows and therefore have an own surface, a.k.a. backing store.
                                                                                                                                                      
                                                                                                                                                      
XDirectFB Options:
                                                                                                                                                      
-defaultOpacity   <opacity>   set the default opacity for toplevel windows,
                              value ranges from 1 (almost invisible) to 255 (fully opaque).
-unfocusedOpacity <opacity>   set the opacity used for unfocused toplevel windows,
                              value ranges from 1 (almost invisible) to 255 (fully opaque).
-enableUnfocused              enable usage of unfocused opacity value.
-enableFadeIn                 enable fade in of showing windows.
-enableFadeOut                enable fade out of hiding windows.
-enableRoot                   enable root window, still experimental.
-displayLayer <ID>            choose display layer (0=primary, for other IDs try "dfbinfo").
                                                                                                                                                      
                                                                                                                                                      
XDirectFB is written by Denis Oliver Kropp <dok@directfb.org>.
It's heavily based on XDarwin and some KDrive code.
                                                                                                                                                      
Short installation instructions:
                                                                                                                                                      
- Check out module "xc" from XFree CVS (www.xfree.org)
- Apply patch "xc-directfb.diff" with "-p0" within "xc/"
- Copy directory "programs/Xserver/hw/directfb" into "xc/programs/Xserver/hw/"
- Copy files in "config/cf/" into "xc/config/cf/"
- Adjust "xc/config/cf/host.def"
- Run "make World", lean back, run "make" for safetiness, run "make install".
                                                                                                                                                      
The default installation directory (defined in host.def) is /usr/local/X11R6.
</readme>
                                                                                                                                                      
Basically, it's a patch for the xfree86 source package generating a XDirectFB binary. Only this binary is different from the ordinary xserver-xfree86 installation.
                                                                                                                                                      


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux arkas 2.4.24 #1 Wed Jan 7 15:43:26 CET 2004 i686
Locale: LANG=C, LC_CTYPE=C



--- End Message ---
--- Begin Message ---
Hi,

Micha Nelissen <micha@neli.hopto.org> (23/04/2004):
> Sorry, here. Taken from
> http://directfb.org/download/XDirectFB/XDirectFB-1.0-rc5.tar.gz.

thanks. Since that's not a Debian bug, I'd suggest talking to upstream
to get that considered/discussed. See:
  http://bugs.freedesktop.org/
  http://wiki.x.org/wiki/Development/Documentation/SubmittingPatches

We're unlikely we do that on our own, so I'm closing this bug report.

KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: