On Mon, Dec 1, 2008 at 8:40 AM, RD Thrush <[EMAIL PROTECTED]> wrote:
>>>>>> "j" == Jason Beaudoin <[EMAIL PROTECTED]> writes:
> j> [ ... snip ... ]
>
> j> so my question: have other folks run into the 0 byte package behavior
> j> before, or are there others with /usr/ports as a symlink but without
> j> any other problems?
>
> j> I understand that I can remove the FETCH_PACKAGES flag and this will
> j> circumvent the problem, but circumvention isn't resolution; I am
> j> curious if I am doing something wrong, of if something really is
> j> broken.
>
> I've symlinked /usr/ports for years and haven't noticed any related
> problems building ports for i386 and amd64. I don't use
> FETCH_PACKAGES so can't comment about that.
mmm, tobais pointed out we should just use PORTSDIR in etc/mk.conf.
> Here's a snippet from one machine.
> x2:build/packages 420>ll /usr/ports
> lrwx------ 1 root wheel 28 Nov 12 2007 /usr/ports ->
> ../pub/OpenBSD/current/ports
> x2:build/packages 421>grep ports /etc/mk.conf
> WRKOBJDIR=/usr/obj/${MACHINE_ARCH}/ports
> PKG_TMPDIR=/usr/obj/${MACHINE_ARCH}/ports/tmp
> PLIST_DB=/usr/obj/${MACHINE_ARCH}/ports/plist_db
> LOCKDIR=/usr/obj/${MACHINE_ARCH}/ports/locks
>
> Regards, Bob
>
thanks!
the chroot is still a mystery.
regards,
~Jason
