Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Apr 2013 18:53:05 +0200
From:      Matthias Petermann <>
To:        Matthew Seaman <>
Subject:   Re: Managing conflicts between ports (same package with multiple maintained versions)
Message-ID:  <>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Thanks Matthew,

your recommendation works for me. As I expect from time to time also an 
older version getting EOL'd, the amount of versions to look ahead can be 
estimated quite well.

Kind regards,

On 04/21/13 17:57, Matthew Seaman wrote:
> On 21/04/2013 10:24, Matthias Petermann wrote:
>> root@compaq:/usr/ports/finance/trytond # portlint -AC
>> [...]
>> FATAL: Package conflicts with itself. You should remove "trytond-*" from
>> 1 fatal error and 4 warnings found.
>> root@compaq:/usr/ports/finance/trytond #
>> So it looks like I need to explicitly specify the conflicting versions,
>> e.g. in Tryton 2.4 Makefile put:
>>      CONFLICTS=      trytond-2.6.*
>> But this will force me to update the 2.4 Ports everytime a new series of
>> Tryton gets introduced.
> The usual idiom would be to use a more complex globbing expression,
> perhaps like so:
> CONFLICTS=	trytond-2.[012356789].*
> However clearly this won't account for all possible future versions.
> The thing you have to ask yourself is 'will the upstream be releasing
> new version series so frequently that I need to add code to all the
> tryton ports to account for it?'  It may well be the case that updating
> the CONFLICTS setting in all the ports for the different streams
> whenerver a new stream is released really is the most effective solution.
> 	Cheers,
> 	Matthew

Want to link to this message? Use this URL: <>