Re: Installation Consensus
От | Dave Page |
---|---|
Тема | Re: Installation Consensus |
Дата | |
Msg-id | 50088.80.177.99.193.1053159012.squirrel@ssl.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Installation Consensus ("Adam H. Pendleton" <fmonkey@fmonkey.net>) |
Список | pgadmin-hackers |
It's rumoured that Adam H. Pendleton once said: > This can be overriden by using "./configure > --prefix=/usr/local/pgadmin3" so then you get: > > pgadmin3 -> /usr/local/pgadmin3/bin > ui/common/*.xrc -> /usr/local/pgadmin3/share/pgadmin3/ui/common > tips.txt -> /usr/local/pgadmin3/share/pgadmin3/ > > It seems to me that if we're going to use Autoconf, then it's best to > stay within the framework of the existing Autoconf installation > directory structure, so that "./configure" behaves the way a normal > autoconf user would expect (much like changing --with-libpq to > --with-pgsql). > > What does everyone think? I was discussing this with Andreas the other day. The fielsystem standard clearly suggests using /usr/local/ as the installation prefix, however as a sysadmin myself, I much prefer /usr/local/appname to keep apps completely seperate from each other. In reality I think most software does this. I'm iun the middle of building a new webswerver which has a large number of PHP dependencies. Probably 90% of what I've installed so far went into /usr/local/appname. The notable exception was the Informix Client SDK which wanted /opt/informix! Your layout under <install prefix> sounds fine. Regards, Dave
В списке pgadmin-hackers по дате отправления: