cvs commit: ports/mail/thunderbird Makefile distinfo ports/mail/thunderbird/files patch-mozilla-xpcom-reflect-xptinfo-src-xptiInterfaceInfoManager.cpp

[Alexey Dokuchaev]

On Mon, Dec 13, 2010 at 10:29:05AM +0100, Beat Gaetzi wrote:
> On 13.12.2010 06:25, Alexey Dokuchaev wrote:
> > On Fri, Dec 10, 2010 at 02:51:59PM +0000, Beat Gaetzi wrote:
> >> beat        2010-12-10 14:51:59 UTC
> >> [...]
> >>   - Replace CONFLICTS with CONFLICTS_INSTALL
> > 
> > Can you please explain this part?
> 
> Sure :) Conflict handling has been reworked and this was committed two
> weeks ago:
> http://lists.freebsd.org/pipermail/freebsd-ports/2010-December/064761.html

Did I miss it, or there were no discussion or proper review?

> I've submitted a patch which updates the porters handbook with the new
> conflict handling. This patch is currently under review but I expect
> that it will be committed soon.

Honestly, with all due respect, I currently fail to see what benefits this
new CONFLICTS thing brings us at the obvious expenses of diversity and
excessive complication; miwi@'s commit message to bpm is not very helpful.
Separating Cs into C_B and C_I suggest that there are at least comparable
number of ports that require each one, but I've only seen ports conflict
because they install the same files.  Can you give us a list of ports
that really fail to *build* when one of them is installed?  If there way
to fix this (e.g. install includes/libraries in slightly different place)?

Even if this new feature is actually useful to people, how about making
CONFLICTS default to CONFLICTS_INSTALL (this seems to be the obvious
choice)?  Otherwise I fear that eventually 99% of conflicting ports will
simply turn into CONFLICT_INSTALL ones.  Same shit, but now 8 characters
longer and does not line up nicely with most of the knobs in Makefile.

./danfe