Subject: Re: Changing from /var/db/pkg
To: Jachym Holecek <>
From: Johnny C. Lam <>
List: tech-pkg
Date: 03/04/2005 10:38:05
Jachym Holecek wrote:
>>>I think it's simpler to just create a utility to move the old database
>>>to the new location, and to just hardcode using the new location from
>>>that point forward.
>>You're right, and the package tools could do that automatically. Or perhaps
>>it's fine if they just ask the user to run the tool, if there's any doubt.
> Just one thing -- some scripts under /var/db/pkg/*/ hardcode the value
> of LOCALBASE. Would this be a problem if the directory is NFS-shared
> between multiple hosts, each of them having different LOCALBASE setting?

This isn't a problem we have to worry about.  You can't put the same 
packages into different places on different hosts because packages 
hardcode the ${LOCALBASE} value into themselves in many different 
places, e.g. where they look for share libraries, where they look for 
data files, etc.  At the very least you must either create either a 
symlink or a null-mount so that the packages can find themselves by 
referring to the ${LOCALBASE} with which they were built.


	-- Johnny Lam <>