On Mon, Aug 21, 2006 at 01:16:22PM +0100, Florent Thoumie wrote:
> On Mon, 2006-08-21 at 07:56 -0400, Kris Kennaway wrote:
> > On Mon, Aug 21, 2006 at 12:27:20PM +0100, Florent Thoumie wrote:
> > > On Mon, 2006-08-21 at 07:07 -0400, Kris Kennaway wrote:
> > > > On Mon, Aug 21, 2006 at 08:09:45AM +0200, Raphael H. Becker wrote:
> > > > >
> > > > > Hi Florent,
> > > > >
> > > > > PKGDIR is ambiguous in the context of ports and packages.
> > > > >
> > > > > I set PKGDIR=/some/where/my/pkg in my /etc/profile which causes the
> > > > > ports to fail badly creating any packages:
> > > > >
> > > > > It is used in ports/Mk/bsd.port.mk:
> > > > > # PKGDIR - A directory containing any package creation
> > > > > # files.
> > > > > # Default: ${MASTERDIR}
> > > > > [...]
> > > > > PKGDIR?= ${MASTERDIR}
> > > > >
> > > > > Havin set PKGDIR statically is a very bad idea here.
> > > >
> > > > Yes, PKGDIR is incorrect in this usage. The documented place where
> > > > packages are stored is:
> > > >
> > > > # PACKAGES - A top level directory where all packages go
> > > > (rather than
> > > > # going locally to each port).
> > > > # Default: ${PORTSDIR}/packages
> > > > #
> > >
> > > PACKAGES is a better choice than PKGDIR, but I'd like to avoid confusion
> > > between "cached" packages (as in, copies of downloaded packages), and
> > > "home-brewed" packages.
> >
> > Not sure there is a need to; they're both just packages.
>
> I think there is, or there should be another subdirectory under PACKAGES
> to tell where the packages come from. Like what apt does, something like
> ${PACKAGES}/ftp.freebsd.org.packages.6.stable/All/blah.tbz.
>
> You definitely don't want to mix packages from different sources, or
> made from different ports trees.I don't really see the need for this; but if you want to go this route there are other tools that also need to be taught about the proposed new directory layout). Kris
pgp6ioLPyVFZ8.pgp
Description: PGP signature
