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]

Re: [PATCH]: mknetrel builds Guile #4: genscript


----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
To: <cygwin-apps@cygwin.com>
Sent: Wednesday, July 10, 2002 1:49 PM

> This is counter to the RPM (and mebbe deb?) concept of "shipping
> pristine sources".  Is there some way to do this?

deb ships pristine sources.

> unpack -src, giving:
> foo-1.2-3.mknetrel
> foo-1.2-3.patch
> foo-1.2.tar.gz
>
> and then running 'mknetrel -@ foo' does what one would expect? ('-@' is
> placeholder 'cause I can't remember the correct options right now)

What I don't understand is the sudden rush. We are mere months away from
full deb or rpm support - why try to shoehorn the existing tarball
orientated tools into the same functionality these more mature tools have
developed?

Getting setup.exe to support multiple source files (download the patch,
scripts and metainfo separately) is mostly-trivial. I've not done that yet
because there are more end-user issues on my plate.

Getting rpmfind or apt-get to operate is straightforward if laboursome today
(write a script to generate a Packages and Sources Releases file set for the
three curr/prev/exp tags from setup.ini.... something that Chris can call
from the end of upset). A similar approach operates to tell rpmfind what
tarballs we have available (but we need rpm file support for this one).

I could go on...

Rob


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]