On Wednesday 23 March 2005 20:29, Elan Ruusamäe wrote: > On Wednesday 23 March 2005 20:11, Jakub Bogusz wrote: > > On Mon, Mar 21, 2005 at 06:07:34PM +0100, Andrzej Augustynowicz wrote: > > > Dnia sobota, 5 marca 2005 11:51, Elan Ruusamäe napisał: > > > > please see horde.spec (imp.spec, chora.spec, ...) how to do > > > > apache1/apache2 config changes, ie apache version independant > > > > package. > > > > > > > > probably should add the information to devel-hints-en ? > > > > > > Maybe it would be a good solution to run this section as trigger for > > > apache1 and apache2 ? > > > for example, you want to install apache1 when had a lot of php programs > > > installed, and support will be auto added by triggers > > > > Note that if one installs _both_ versions of apache simultaneously, they > > in almost all cases will serve different contents. > > So it's most likely to be unwanted to automatically link app configs to > > both apaches. > > And relinking such config on each upgrade of given apache version will > > be _extremely annoying_. > > and if the package itself is upgraded, the config is (again) linked anyway. > (the current situation is so) > ... i've felt that annoyance :( > > perhaps change the %post script to place link only on first install? > ie check for [ $1 = 1 ]? > > hmm, but placing the link only on first install (eighter package or apache) > is possible with triggers too. (the same $1 or $2 check) updated template-apache-package.spec, so that configuration is linked to apache configration dir only on package's initial install. the link is not (re)created upon upgrades (eighter package or apache)
> but i really like the config placement %trigger idea :) -- glen _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
