Dislike the way port conflicts are handled now
pav at FreeBSD.org
Sat Jan 16 20:53:39 UTC 2010
Greg Larkin píše v so 16. 01. 2010 v 13:58 -0500:
> That's exactly what I proposed. The bsd.port.mk could be patched to
> support a new variable ("EARLY_CONFLICT_CHECK=yes" or somesuch) that
> shifts the check-conflict target from its old position (part of the
> install sequence) to its new position (fetch?).
> The default behavior (no mods to /etc/make.conf) would revert to the old
> conflict checking method. This may be something for portmgr@ to chime
> in on, and I'm cc'ing them now. There could be other reasons for this
> change that I'm unaware of.
What is the particular scenario that the new conflicts handling broke
for you? Often you really want to ignore locally installed packages and
then it's better to override LOCALBASE to /nonex or something similar,
instead of disabling conflict handling...
Pav Lucistnik <pav at oook.cz>
<pav at FreeBSD.org>
It's the classic Microsoft security-bulletin formula: "The vulnerability
is important (never dangerous); you have nothing to fear and no reason
to regret trusting us; we have no intention of apologizing for it or
even explaining it adequately; now go get your patch, shut up, and be
grateful nothing bad has happened. -- The Register
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?=
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20100116/06e1a018/attachment.pgp
More information about the freebsd-questions