Christopher Faylor [EMAIL PROTECTED] writes:
That's swell. However, I'm not going to be moving. I don't want a
whatever.sh script showing up in my sources.
Yes, I understand. There was quite a thread about this...
So, I guess this is another option. If you submit it as an option,
I'll
Robert Collins wrote:
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?
Good point. There is no need to method
Robert Collins wrote:
My 2c: We settled on method 2 as a interim step before rpm or deb, to avoid
build yet another tool.
Doh! Correct.
Enough said.
Yep. Don't method 2-ize mknetrel
--Chuck
Christopher Faylor [EMAIL PROTECTED] writes:
On Tue, Jul 09, 2002 at 02:14:37AM +0200, Jan Nieuwenhuizen wrote:
- autogenerate cygwin build script: $package.sh
This looks like a prepackage function to me. No need to modify mknetrel.
I think that you do not understand. This will
Jan Nieuwenhuizen wrote:
The script is a requirement for Method2, and I'd like to slowly move
towards that packaging method.
http://www.cygwin.com/setup.html isn't written in stone. If we want to add a method
3 which is:
donwload current mknetrel
copy the included script 'pkgname'
Charles Wilson [EMAIL PROTECTED] writes:
If we want to add a method 3 which is:
donwload current mknetrel
copy the included script 'pkgname' into mknetrel/extra (*)
run mknetrel -b
(*) where 'pkgname' is the override script.
That would be fine, too, IMO.
Ah, now that would be smart
Jan Nieuwenhuizen wrote:
Ah, now that would be smart thing to do, why didn't I think of that?
What about picking a directory for extra right now, let's say:
/usr/share/mknetrel/extra
and have individual packages all unpack their extra script there
(maybe even junk most extra's
Jan Nieuwenhuizen wrote:
Charles Wilson [EMAIL PROTECTED] writes:
If we want to add a method 3 which is:
donwload current mknetrel
copy the included script 'pkgname' into mknetrel/extra (*)
run mknetrel -b
(*) where 'pkgname' is the override script.
That would be fine, too, IMO.
Ah, now
Nicholas Wourms wrote:
What about picking a directory for extra right now, let's say:
/usr/share/mknetrel/extra
and have individual packages all unpack their extra script there
(maybe even junk most extra's from mknetrel-cvs itself)?
Not yet. Since all of the scripts current in
On Tue, Jul 09, 2002 at 06:05:51PM +0200, Jan Nieuwenhuizen wrote:
Christopher Faylor [EMAIL PROTECTED] writes:
On Tue, Jul 09, 2002 at 02:14:37AM +0200, Jan Nieuwenhuizen wrote:
- autogenerate cygwin build script: $package.sh
This looks like a prepackage function to me. No need to
Hmm. It's sort of sad when I make the effort to read the entire thread
but still miss the point anyway.
Why not just have mknetrel use a mknetrel file in the source directory
if it finds one? I've been thinking about doing this for a while.
Then there is no need to decide on a location for
Charles Wilson wrote:
Now, stop me if I get too 'method 2ish', but:
[snip]
unpack -src, giving:
foo-1.2-3.mknetrel
foo-1.2-3.patch
foo-1.2.tar.gz
Yes, this looks an awful lot like 'method 2' -- and we've got perfectly
good example shell scripts for doing things the 'method 2' way.
- Original Message -
From: Charles Wilson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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:
- Original Message -
From: Charles Wilson [EMAIL PROTECTED]
To: Charles Wilson [EMAIL PROTECTED]
Sent: Wednesday, July 10, 2002 1:54 PM
unpack -src, giving:
foo-1.2-3.mknetrel
foo-1.2-3.patch
foo-1.2.tar.gz
Yes, this looks an awful lot like 'method 2' -- and we've got
14 matches
Mail list logo
