Re: Strange CONFLICTS definitions render pkgin full-upgrade impossible

["Aleksej Lebedev" <root%zta.lk@localhost>]

These are indeed possible solutions, thanks.

Regarding the fix in the package though I noticed that fixing the CONFLICTS declaration doesn't solve the problem for the user who already has the incorrect package installed as pkgin checks incoming packages against LOCAL_CONFLICTS.
So once the user has the old version of ruby25-treetop there is no way to upgrade regardless if the problem was fixed in the new package or not :-(.

--
Aleksej Lebedev

> 
> So there are two better places to do work here if we want to avoid this 
> problem in the future:
> 
>   - For each proposed CONFLICTS entries, perform a pmatch against the
>     target PKGNAME during pkg_create, and abort if there is a match.
>     This will ensure we never create and distribute a broken package.
> 
>   - Add a similar check to pkglint based on Makefile contents.  This will
>     ensure we never commit a broken package, assuming the committer runs
>     pkglint before committing...
> 
> The pkg_create patch should be trivial.  The pkglint patch may be more 
> complex and may not catch all cases, as it would need to compute all 
> possible PKGNAME variations.
> 
> -- 
> Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com
>