This is the mail archive of the
mailing list for the Cygwin project.
Re: Package making guidelines question
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Max Bowsher <maxb at ukf dot net>
- Cc: cygwin-apps at cygwin dot com
- Date: Tue, 19 Apr 2005 10:42:33 -0400 (EDT)
- Subject: Re: Package making guidelines question
- References: <043b01c544c6$7d24bc20$6508a8c0@chimaera>
- Reply-to: cygwin-apps at cygwin dot com
On Tue, 19 Apr 2005, Max Bowsher wrote:
> When a packager follows a pseudo-"Method 2" approach, using a home-grown
> script not based on generic-build-script, how closely must the naming and
> behaviour of the script follow the official template?
I don't think there is a particular set of requirements on this, but at
the very least, when extracted by setup.exe to /usr/src, the script should
not produce a name conflict with either other source packages or, more
importantly, previous versions of the sources for the same package, which
leaves very little room for variation in naming.
> What degree of automation is required in terms of setup?
> Do we require that the included script be capable of rebuilding the
> packages entirely by itself, or is it permissible to require manual tar,
> patch, etc., commands first?
Behavior-wise, the script should, IMO, at the very least provide a way of
creating a patched source directory. I don't think having full automation
is (or should be) a requirement. As long as the package README is clear
on what steps are needed, it's ok to require manual steps towards the
Again, I don't set the policy for these things, so the above is just my
|\ _,,,---,,_ email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ firstname.lastname@example.org
|,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