Re: autoconf make install
От | Dave Page |
---|---|
Тема | Re: autoconf make install |
Дата | |
Msg-id | 03AF4E498C591348A42FC93DEA9661B83AF093@mail.vale-housing.co.uk обсуждение исходный текст |
Ответы |
Re: autoconf make install
|
Список | pgadmin-hackers |
> -----Original Message----- > From: Andreas Pflug [mailto:Andreas.Pflug@web.de] > Sent: 13 May 2003 22:34 > To: Dave Page; pgadmin-hackers@postgresql.org > Subject: Re: autoconf make install > > > Dave Page wrote: > > >I think /usr/local/pgadmin3 is the right place. > /usr/X11R6/bin should > >be for components of X11R6 that came with the OS, whereas > /usr/local/ > >is specifically for additional programs installed by the > local admin. > >If it ever gets popular enough to ship with 'pgLinux' for > example :-) > >then /usr/pgadmin3 would seem sensible. > > > Should we really invent a new directory, requiring changes to > PATH? Why > not using /usr/local/bin? In this case, we shouldn't use > /usr/local/bin/ui/*, but something distinctive as > /usr/local/bin/pgadmin.ui/*. Well technically the filesystem standard does say we should use /usr/local/bin. The gui components should probably be elsewhere (/usr/local/share springs to mind, but that *should* be architecture independent data which you could argue the xrc's are not). As a sysadmin though, I prefer a program specific structure under /usr/local/xxx. It makes it so much easier to seperate out what files belongs to what package. Can make a mess of your path and ld.so.conf admittedly, but then I usually type full paths anyway. Some also consider adding /usr/local/bin/ to the path to be a bad idea though I never quite figured out why. Thought or comments from anyone else? Regards, Dave.
В списке pgadmin-hackers по дате отправления: