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 code/
> "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
>> fi
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 . -print | sed 's,^/tmp/install,,'
> rm -rf /t
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
On Jan 23, 2001, Alexandre Duret-Lutz <[EMAIL PROTECTED]> wrote:
> INSTALL_STRIP_PROGRAM=$$(topsrc_dir)/$(install_sh) -s
> and then
> install-strip:
> $(MAKE) INSTALL_PROGRAM='$(INSTALL_STRIP_PROGRAM)' install
> So that $(topsrc_dir) gets evaluated in the sub-make. From
> the simulati
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
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 Gu
Tom Tromey wrote:
> ...
> Michael>The downside is that you have to somehow clear the
> Michael>existing list file before doing this, or only do it
> Michael>once, so that you have the correct set of files...
>
> I don't understand this.
Basically, the install-sh hack woul
> 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 h
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
AC_PRO
> "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
Micha
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
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, ret
"Derek R. Price" wrote:
> ...
> Due to security concerns, you're obviously never going to be able
> to install files owned by root without root privledges, but are
> you really telling me that these systems require you to _build_
> packages as root?
For all practical purposes, yes.
For Debian, t
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
> w
This is the result of the two previous patches on the fileutils:
@@ -22693,12 +22653,7 @@
s,@ECHO_C@,$ECHO_C,;t t
s,@ECHO_N@,$ECHO_N,;t t
s,@ECHO_T@,$ECHO_T,;t t
-s,@CFLAGS@,$CFLAGS,;t t
-s,@CPPFLAGS@,$CPPFLAGS,;t t
-s,@CXXFLAGS@,$CXXFLAGS,;t t
-s,@FFLAGS@,$FFLAGS,;t t
s,@DEFS@,$DEFS,;t t
-s,
16 matches
Mail list logo