Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: xorg-x11-server-Xgl
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192436
------- Additional Comments From alcapcom(a)gmail.com 2007-03-07 06:28 EST -------
(In reply to comment #31)
Alphonse,
Hi Steffan,
Per "What do you thing of such a solution to replace the crazy
post script?",
please take a look at what has been done in Xgl-settings.
There is some problem with this type of solution,
so I'm not sure if such a solution can be approved by a reviewer.
1. Traditionally X is started on the display :0, but that is not possible if we
start Xgl from GDM (dislay :0 should already used by GDM)
2. There are 3 log files for X (Xorg.0.log, Xorg.1.log and Xorg.93.log) that
should appear strange for the end user.
3. For each WM available for fedora, we needs a .desktop file (GDM session menu
can quickly look too big)
I we start GDM with Xgl all these problem can be forgotten.
I think the next step is to make sure we are both not duplicating
work. If we
need to setup a VCS for this, let's do it.
I am not a partisan of duplicate work too ;)
Sorry for my ignorance, but what is VCS?
Per comment #20, we need to make sure we comment how to checkout the
source from
upstream. This means we need to be able to git-clone something such as a tag or
a revision.
Last specfile contain this line, is that not enough?
# git tar-tree xgl-0-0-1 xorg-x11-server-Xgl | bzip2 >
%{name}-%{version}-%{release}.tar.bz2
We should also look to get these package not only building on FC6,
but on
rawhide also. Last test showed these do not build on rawhide.
Personally, I have not enough internet band-width to download and to keep
up-to-date more than one branch at once.
If you can take a look on the rawhide problem, it should be very appreciated.
Thanks,
--
Configure bugmail:
https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.