ports structure and improvement suggestions
Ulrich Spoerlein
uspoerlein at gmail.com
Sun May 14 08:08:06 UTC 2006
martinko wrote:
> Scot Hetzel wrote:
> > The problem with pkgtools.conf (and all the other port management
> > tools) is that it only works for the port that you are currently
> > building. If that port has dependancies, the settings in
> > pkgtools.conf for the dependancies are not applied to the dependent
> > port. Instead you need to build the dependent ports first.
> >
> > Where as putting the variable into make.conf, will allow the dependent
> > port to always build with that setting.
>
> why is it so ??
> i discovered this some time ago but have always been wondering why does
> it work this "unlogical" way..
Very simple,
portinstall tries to install port A with settings from pkgtools.conf.
make(1) decides port A depends on port B, which is not yet installed.
make(1) will install B (*without* the settings in pkgtools.conf, of
course).
The workaround would be to 'portinstall B; portinstall A', but this is
impractical of course.
Ulrich Spoerlein
--
PGP Key ID: 20FEE9DD Encrypted mail welcome!
Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD
Which is worse: ignorance or apathy?
Don't know. Don't care.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20060514/a402982c/attachment.pgp
More information about the freebsd-ports
mailing list