This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: [PATCH] generic-build-script
On Wed, 22 Jun 2005, Max Bowsher wrote:
Igor Pechtchanski wrote:
> 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.
Yes, true. Particularly the "unpack()" function, which only handles
.tar.* files for now, and needs to be redefined for other packaging
methods.
It's perhaps worth mentioning that I don't maintain any per-package
customizations to the g-b-s directly, but instead have written myself a
Python script which modifies the basic g-b-s according to a per-package
rules file.
For example, here are my rules for neon:
ConfigureArg --enable-shared
ConfigureArg --disable-static
ConfigureArg --with-ssl
SubPackage libneon24-$VER-$REL.tar.bz2 usr/bin/cygneon-24.dll
The script is attached.
Thanks, I'll take a better look at the script later, but at the very least
the configure args can be factored out into a variable. FWIW, I don't
have any ideas on how to handle subpackages properly, but perhaps your
script contains some hints on that as well.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT