Re: Strange CONFLICTS definitions render pkgin full-upgrade impossible

[nia <nia%NetBSD.org@localhost>]

On Thu, May 20, 2021 at 05:03:08PM +0200, Aleksej Lebedev wrote:
> However I checked if there are other packages with that kind of definition left in pkgsrc and I found some:
> 
> $ find textproc -name Makefile | xargs grep ^CONFL | grep ruby
> textproc/ruby-bluecloth/Makefile:CONFLICTS+=	ruby[1-9][0-9]-bluecloth-[0-9]*
> textproc/ruby-rttool/Makefile:CONFLICTS+=	ruby[1-9][0-9]-rttool-*
> textproc/ruby-amrita/Makefile:CONFLICTS+=	ruby[1-9][0-9]-amrita-*
> textproc/ruby-maruku/Makefile:CONFLICTS+=	ruby[1-9][0-9]-maruku-*
> 
> We happen not to use those but I am quite sure they will cause the same problem with pkgin upgrade.
> 
> My question: is it just a mistake or is there some kind of good indent behind those CONFLICTS defs?

These packages are self-conflicting between different ruby
versions (e.g. ruby26-bluecloth and ruby25-bluecloth can't be
installed at once) because they install an unprefixed/suffixed
binary to bin/.

This is pretty bad practice, there should be a separate package
for the binary if the ruby library is independentaly useful,
otherwise they shouldn't be versioned.