On 27/06/2010 20:04, Lev Serebryakov wrote:
Hello, Freebsd-ports.
I understand, that this change (ports/137855, bsd.port.mk:1.632) was
made 6 months ago, but I've
noticed it only now (twice in one day!).
Am I only person, who thinks, that this change is HUGE POLA
2010/6/27 Lev Serebryakov l...@freebsd.org:
Hello, Freebsd-ports.
I understand, that this change (ports/137855, bsd.port.mk:1.632) was
made 6 months ago, but I've
noticed it only now (twice in one day!).
Am I only person, who thinks, that this change is HUGE POLA
Had the same here when trying to upgrade things, I don't want to
have to uninstall the current version before I can build the new
one only to find out there is some issue and have to roll back.
I've ended up commenting out the conflicts and ignoring them,
which I'm sure is not the desired
make -DDISABLE_CONFLICTS
On 6/27/2010 2:04 PM, Lev Serebryakov wrote:
Hello, Freebsd-ports.
I understand, that this change (ports/137855, bsd.port.mk:1.632) was
made 6 months ago, but I've
noticed it only now (twice in one day!).
Am I only person, who thinks, that
On Sun, 27 Jun 2010, Lev Serebryakov wrote:
Hello, Freebsd-ports.
I understand, that this change (ports/137855, bsd.port.mk:1.632) was
made 6 months ago, but I've
noticed it only now (twice in one day!).
Am I only person, who thinks, that this change is HUGE POLA
violation?
On Sun, 27 Jun 2010, Garrett Cooper wrote:
I would think that the CONFLICTS detection should only be a
warning in the first run-through, and become a hard error when you try
and run make install.
I agree.
FWIW,
Doug
--
Improve the effectiveness of your Internet presence with
