On Fri, Dec 12, 2014 at 03:13:44PM +0200, Heikki Linnakangas wrote: > On 12/12/2014 03:11 PM, Heikki Linnakangas wrote: > >On 12/12/2014 03:07 PM, Peter Eisentraut wrote: > >>On 12/9/14 4:10 PM, Alvaro Herrera wrote: > >>>Maybe it makes sense to have a distinction between client programs and > >>>server programs. Can we have src/sbin/ and move stuff that involves the > >>>server side in there? I think that'd be pg_xlogdump, pg_archivecleanup, > >>>pg_upgrade, pg_test_timing, pg_test_fsync. (If we were feeling bold we > >>>could also move pg_resetxlog, pg_controldata and initdb there.) > >> > >>I was thinking about that. What do others think? > > > >Sounds good. We already separate server and client programs in the docs, > >and packagers put them in different packages too. This should make > >packagers' life a little bit easier in the long run. > > src/sbin might not be a good name for the directory, though. We're > not going to install the programs in /usr/sbin, are we? Maybe > src/server-bin and src/client-bin.
I am confused by the above because you are mixing /src and /bin. If we install the binaries in new directories, that is going to require multiple adjustments to $PATH --- that doesn't seem like a win, and we only have 25 binaries in pgsql/bin now (my Debian /usr/bin has 2306 binaries). I assume I am misunderstanding something. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers