David O'Brien <[EMAIL PROTECTED]> types:
> > Wherease "PREFIX clean" means "all installed files are in the PREFIX
> > tree",
> > I intend "LOCALBASE clean" to mean "all files installed by other ports
> > are looked for in the LOCALBASE tree".
> If all ports are PREFIX clean, you will have that. Thus it doens't need
> to be discussed separately.
Using the two definitions above, the first sentence is false.
In particular, assume that the port APort depends on BPort in some
way, and is PREFIX clean. That means that everything in APort is
installed in PREFIX, and all APorts references to things in APort look
for them there.
Neither of those statements precludes APort from looking for things
that are part of BPort directly in /usr/local instead of in
LOCALBASE. Doing so would make APort PREFIX clean while it was not
I've only seen this break during the build. Most typical is the
applications configuration software looking in /usr/local for an
include file or library from BPort instead of looking in
LOCALBASE. Some things assume that $(LOCALBASE)/bin is in the path,
which is probably true for most users. However, the scripts provided
by FreeBSD in /root add /usr/local/bin, *not* $(LOCALBASE)/bin. So
such runtime dependencies don't break for users, but do for root -
which means they are more likely to be noticed if they are build
dependencies than if they are run dependencies.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message