cvs commit: src/nrelease Makefile mk.conf.pkgsrc
dillon at apollo.backplane.com
Tue Aug 14 11:03:11 PDT 2007
:Were else should it write to? Seriously, the default is the only
:consistent behaviour possible. If you run it as user, you don't have
:access to any system locations. If you have more than one tree, you
:don't get collissions by default etc.
:Many installations have large /usr filesystems, so it doesn't really
:matter whether the work directories are in the main tree or under
:/usr/obj. I'd even argue that keeping it in the default tree can make it
:a bit more obvious when stale work directories are left behind as cvs
The main reason is that when you have more then one machine it's a
major waste of resources to have to maintain a local copy of /usr/pkgsrc
on every machine when all you really want to do is maintain it on one
machine and use read-only NFS mounts on all the others.
Mixing maintained data with work data makes it impossible to distribute
/usr/pkgsrc as a read only mount and also means one winds up backing up
the work data along with everything else in /usr, which is severe waste
of backup space. Having distfiles in /usr/pkgsrc creates similar
Fortunately /usr/pkg/etc/mk.conf can be edited to fix this and
/usr/pkgsrc/distfiles can be turned into a softlink to get around the
distfiles location problem. But the default still sucks big-time.
<dillon at backplane.com>
More information about the Commits