Michael C . Wu <[EMAIL PROTECTED]> types:
> I know I should not jump into this bikeshed.  But IMHO, whereever
> we have our packages install to, we should also place
> our ports metadata (/var/db/pkg) and the ports skeleton in the
> same place, preferably a mountpoint.  This allow me to switch
> between different sets of installation with ease.  (No, please
> do not tell me to change PREFIX and mv /usr/local /usr/local.bak)
> With this setup, I can rm -rf <whatever place this goes>, and
> have a clean system again.  For the ports developers, we can 
> switch between configurations without the need for chroots or
> jails taking up disk space.

Ok, I can see wanting that. And I can see how it would be handy for
ports developers. But my instant reaction was "yuch". The reason for
that is that, unlike the contents of ${PREFIX}, the contents of the
ports metadata is *not* generally recreatable from the /usr/ports
tree. This means it's more precious, and you might want to back it up
more frequently, etc.

While some method for ports developers to move the metadata (say an
environment variable) should be provided, I think the above is a good
reason for leaving the default as is.

BTW, pkg_add (at least) honors the environment variable PKG_DBDIR to
set the location of the ports metadata directory. Is there some reason
you can't just set that to /usr/local/etc/db/pkg or some such?

Final comment - I wish more ports developers *would* set PREFIX.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to