Evolve 5.5.0 released

[Pierre-Yves David]

On 11/01/2016 04:49 PM, Danek Duvall wrote:
> Pierre-Yves David wrote:
>
>>
>>
>> On 11/01/2016 12:54 AM, Augie Fackler wrote:
>>>
>>>> On Oct 31, 2016, at 19:53, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
>>>>
>>>>
>>>>
>>>> On 11/01/2016 12:45 AM, Augie Fackler wrote:
>>>>> (+dstufft)
>>>>>
>>>>>> On Oct 31, 2016, at 7:01 PM, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
>>>>>>
>>>>>> This release is compatible from Mercurial 3.4 to Mercurial 4.0.
>>>>>> The next release will probably break this and move evolve into the official 'hgext3rd' namespace package dedicated to 3rd party extensions. But there is some tricky part around this as Python packaging apparently do not know how to remove file installed by previous version when upgrading :-/
>>>>>
>>>>> I thought pip could handle this. dstufft?
>>>>>
>>>>> (I think this is another reason to eschew easy_install.)
>>>>
>>>> I tested using 'setup.py install' and installing the new version did not cleaned the old file. I was sad :-( if Donald have some more data about this (or a pointer to appropriate explanation) I would be very grateful.
>>>
>>> Ah. You probably want to be using `pip install .` instead of `python setup.py install` in all cases.
>>
>> Interesting, thanks. But the issue is not really about me because I could be
>> cleaning up my install myself.
>>
>> How many other user are using the setup.py directly ? Could we have the
>> setup.py abort unless run through pip ? (or any other package manager)
>
> I'm using it as part of the Solaris build (as I am for all other Python
> packages).

Does Solaris has a package manager that is able to properly remove the 
old package file when installing the new one ?

-- 
Pierre-Yves David