This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tue, 21 Jun 2005, Gary R. Van Sickle wrote:
If BASEPKG seems better for the upstream package name,
What about just ${UPSTREAM_PACKAGE_NAME}?
You know, the thought did cross my mind. But the above is just unwieldy enough to remove it from consideration.
OTOH, it would be nice if all of the configuration variables in the GBS (i.e., those that may be changed by the maintainers) were collected in one place, with comments like the one Harold suggested (and Max added).
Problem is, it's not just variables. Any moderately complex package can require all sorts of tweaks.
ConfigureArg --enable-shared ConfigureArg --disable-static ConfigureArg --with-ssl SubPackage libneon24-$VER-$REL.tar.bz2 usr/bin/cygneon-24.dll
Attachment:
gbsmunge.py
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |