Re: More an autopackage

2001-01-23 Thread Michael Sweet
Geoffrey Wossum wrote: ... the job right now. For instance, our packages are supposed to have a pre-install script that does a click-through agreement. I've tried to explain that you can tell the package system (rpm, at least) not to run pre-install scripts and therefore it probably

Re: PATCH: patsubst support

2001-01-23 Thread Pavel Roskin
Hello! Trying to catch up with the mailing lists :-) I'm surprised that this patch has not been applied since October. I believe it's very valuable. I even considered doing it myself. b) default static expansion to off, avoids surprising anyone depending on dynamic expansion by make,

Re: More an autopackage

2001-01-23 Thread Steve Robbins
On Mon, Jan 22, 2001 at 09:49:04PM -0500, Michael Sweet wrote: Rusty Ballinger wrote: ... (What packaging systems only let you create packages as root, and why do they do that? I know rpm *wants* you to be root, but you don't have to be...) Debian's dpkg needs you to run as root;

Re: More an autopackage

2001-01-23 Thread Tom Tromey
"Michael" == Michael Sweet [EMAIL PROTECTED] writes: Michael http://www.easysw.com/epm I haven't tried this, but I read through the web site, and it definitely looks like what I'd like out of an `autopackage'. Michael 1. Provide an install-sh like script that appends the Michael

Automake shooting in its foot

2001-01-23 Thread akim
I tracked down the CXX definition in the fileutils' Makefile.ins, and it's damned stupid... Automake comes with its own set of macros, for instance to set up AM_DEPENDENCIES. Whoever uses automake will include these macros in aclocal.m4. Then automake, when scanning aclocal.m4 will find

Re: More an autopackage

2001-01-23 Thread Geoffrey Wossum
Actually, you could probably steal the script stuff from the portable.c file that shows the license agreement. I wouldn't wait for the response (that would break GUI installers), but at least you can cat out the license agreement to the screen... But just displaying the license doesn't have

Re: More an autopackage

2001-01-23 Thread Michael Sweet
Tom Tromey wrote: ... MichaelThe downside is that you have to somehow clear the Michaelexisting list file before doing this, or only do it Michaelonce, so that you have the correct set of files... I don't understand this. Basically, the install-sh hack would append

Re: More an autopackage

2001-01-23 Thread Alexandre Oliva
On Jan 22, 2001, Michael Sweet [EMAIL PROTECTED] wrote: What it doesn't do (yet) is provide a tool to automate the creation of the list file. make install DESTDIR=/tmp/install find /tmp/install/. ! -name . -print | sed 's,^/tmp/install,,' rm -rf /tmp/install -- Alexandre Oliva Enjoy

Re: More an autopackage

2001-01-23 Thread Michael Sweet
Geoffrey Wossum wrote: Actually, you could probably steal the script stuff from the portable.c file that shows the license agreement. I wouldn't wait for the response (that would break GUI installers), but at least you can cat out the license agreement to the screen... But just

Re: Automake shooting in its foot

2001-01-23 Thread Alexandre Oliva
On Jan 23, 2001, [EMAIL PROTECTED] wrote: So, IMHO, we have just no issue until we release an autoconf --trace aware automake. And frankly, I can't wait :) Automake will be much shorter (less hard coded knowledge on Autoconf), more robust (less hard coded knowledge on Autoconf), and more

Re: More an autopackage

2001-01-23 Thread Ganesan Rajagopal
"Michael" == Michael Sweet [EMAIL PROTECTED] writes: Alexandre Oliva wrote: On Jan 22, 2001, Michael Sweet [EMAIL PROTECTED] wrote: What it doesn't do (yet) is provide a tool to automate the creation of the list file. make install DESTDIR=/tmp/install find /tmp/install/. ! -name .

Re: using pswrap

2001-01-23 Thread trevor
hi Tom, thank you so much for your help! your advice was fantastic. whoops... i just noticed your name on the autotools book! no wonder! anyway, everything you mentioned was documented in the "info" file so you don't have to worry about adding anything. based on your advice i created my