This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: New Maintainer
- From: "Larry Hall (Cygwin X)" <reply-to-list-only-lh-x at cygwin dot com>
- To: cygwin-xfree at cygwin dot com
- Date: Thu, 27 Mar 2008 15:15:33 -0400
- Subject: Re: New Maintainer
- References: <003101c8903c$58792130$c3239681@BULLWINKLE>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: cygwin-xfree at cygwin dot com
DRC wrote:
It's pretty simple. You have to package new new releases of X.org for
Cygwin and support people on this mailing list.
Well, I'm willing to give it a try at least. I know nothing about Cygwin
packaging, but I have experience building X.org on Windows. My project
(VirtualGL) needs Cygwin/X because of its support of the MIT-SHM extension,
and we have access to plenty of build machines.
Sounds terrific! :-)
Is there a spec for which files go in which packages, etc.? Any other
advice to get started, or should I just start downloading and tinkering?
You can find a bunch of info about packaging here:
<http://cygwin.com/setup.html>
The one thing that's somewhat dated is the use of gbs as the packaging
method. I haven't looked but I expect the current X packages use that.
While it's still possible to use, 'cygport' is preferred. But it's still
the choice of the maintainer. It is best to stick with one of the existing
options though since there's some familiarity with them in the community.
I assume that part of the duties are to also feed back patches into the
master X.org repository to fix the Cygwin build, etc.
Yes, definitely.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 429-6305 - FAX
Holliston, MA 01746
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/