This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: New Maintainer
- From: "Yaakov (Cygwin Ports)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-xfree at cygwin dot com
- Date: Thu, 05 Jun 2008 21:45:50 -0500
- Subject: Re: New Maintainer
- References: <003101c8903c$58792130$c3239681@BULLWINKLE> <47EC50B9.4070603@cwilson.fastmail.fm> <20080328141805.GA22873@ednor.casa.cgf.cx> <47ED262B.4020809@cwilson.fastmail.fm>
- Reply-to: cygwin-xfree at cygwin dot com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Charles Wilson wrote:
| The only real difference is that the *nixes would provide only the DLL
| (so) package 'libxext6' and the -devel package 'libxext-devel'; there's
| nothing specific in this case that really needs to go in a "base"
| package 'libxext'. However, in Cygwin's case I've noticed that
| setup.exe (at least in the past) got annoyed if you have:
| foo-*-src.tar.bz2
| libfoo6-*.tar.bz2 (external-source: foo)
| libfoo-devel-*.tar.bz2 (external-source: foo)
| but do not have
| foo-*.tar.bz2
| Maybe this is a bug in setup and we should fix it, or maybe it is not a
| problem anymore. In any case, we need to put the cygwin README, and the
| "normal" README/THANKS/AUTHORS/ChangeLog goobledygook somewhere. Might
| as well be in the (otherwise empty) foo-*.tar.bz2 package.
FWIW, I've just added support for empty packages in cygport; i.e. the
following is now legal:
abi=6
PKG_NAMES="foo libfoo$abi libfoo-devel"
PKG_HINTS="setup lib devel"
PKG_CONTENTS[0]=
PKG_CONTENTS[1]="usr/bin/*-$abi.dll usr/share/doc/"
PKG_CONTENTS[2]="usr/include/ usr/lib/ usr/share/man/man3/"
(The $abi is my trick to make sure I don't miss an ABI change in what
may otherwise appear to be an ordinary version bump.)
| As it happens, Yaakov chose to put the man3 docs in the "main" foo-*
| package, instead of the libfoo-devel-* package. I'd probably do it more
| like the *nixes, in this case. But really, is THIS significant?
No, but I see your point, and future Ports releases will have in the
devel package. (An X11 refresh will have to wait *at least* until I'm
finished with GNOME 2.22, which is in progress.)
Now if I could only figure out that server...
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkhIpN4ACgkQpiWmPGlmQSOpugCgwH7tmnUS9Y8i9VSOw6KY0510
gHAAoIO7jZwSW777UPaEpD8JgYZ+8iqK
=EC8B
-----END PGP SIGNATURE-----
--
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/