svn commit: r365566 - head/Tools/scripts

[Kubilay Kocak]

On 23/08/2014 5:46 PM, Matthias Andree wrote:
> Am 21.08.2014 um 19:21 schrieb Kubilay Kocak:
> 
>> We probably could have used one of these in python@ for cleaning up
>> setuptools (old) and distribute remnants that caused many issues for
>> users as we chased upstream, even with good instructions in UPDATING
>> (since we couldnt cover all cases)
>>
>> I wonder too, to what extent a relatively generic interface for these
>> things might be possible.
> 
> I wonder if an "annotated list" of versions would help the pkg solver
> handle these; if the metadata for a new package lists "Obsoletes:
> blah<3.0" then the solver would automatically remove blah<3.0.
> 
> I haven't investigated how far the automatic solving in pkg works for
> such situations especially if you have the version part of the package
> name as in py27-* and py34-*, or db48 vs. db6.
> 
> Basically it is a question if there are alternative versions to choose
> from on one hand, or on the other hand there is a clear (to the tool,
> anyways) upgrade path for a package that has gone away, like db43 to db5.
> 

I just landed devel/picosat, the SAT solver used in the latest versions
of pkg, and devel/py-pycosat, Python interface to the former.

They might help you answer some of the above questions, let me know if
they do :)

--
koobs