Re: "Meta" packages

[Karl Eichwalder <keichwa gmx net>]

Jim Garrison <garrison users sourceforge net> writes:

> /usr/src/gnome-meta-1.4.0$ ./configure --prefix=/usr --sysconfdir=/etc
> --without-gnome-print
> /usr/src/gnome-meta-1.4.0$ make
> 
> Something like this could be cool because a person would only have to type
> prefix once (and it would be the same for all packages).  Since a small
> amount of people (?) install from tarballs, it may not be worth the extra
> effort and confusion, however.

I'm inclined to agree with you.  Remaining people will use there own
spec files, or the command history, or system wide configuration option
Autoconf offers:

-=-=-=-=-=-=-=-=-=-=-=-=-=- cut here -=-=-=-=-=-=-=-=-=-=-=-=-=-
Setting Site Defaults
=====================

   Autoconf-generated `configure' scripts allow your site to provide
default values for some configuration values.  You do this by creating
site- and system-wide initialization files.

   If the environment variable `CONFIG_SITE' is set, `configure' uses
its value as the name of a shell script to read.  Otherwise, it reads
the shell script `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Thus, settings in
machine-specific files override those in machine-independent ones in
case of conflict.

[...]

-- 
work : ke suse de                          |          ------    ,__o
     : http://www.suse.de/~ke/             |         ------   _-\_<,
home : keichwa gmx net                     |        ------   (*)/'(*)