On Fri, Jun 29, 2012 at 8:53 AM, Michał Górny <mgorny@g.o> wrote:
> On Fri, 29 Jun 2012 14:07:58 +1200
> Kent Fredric <kentfredric@...> wrote:
>
>> On 27 June 2012 19:51, Federico "fox" Scrinzi <fox91@...> wrote:
>> > The main question is: what would you like to have on this dashboard?
>> > Currently (in the development version) there's the possibility to
>> > login and watch/unwatch packages/categories/herds/... and see the
>> > watched stuff in the account dashboard. We're planning on
>> > implementing a weekly(?) custom newsletter based on the packages
>> > you're watching, which features would you like?
>> >
>> > The project repo for the GSoC is here:
>> > https://github.com/volpino/euscan
>> >
>> > Thanks!
>> >
>>
>> For the most part it seems to get upstream / portage versioning right,
>> but occasionally you get miss-matches for some reason.
>>
>> It would be nice to allow to provide some mapping mechanism that
>> existed on the overlay itself to inform euscan how to map upstream
>> versions to downstream ones, but implementing that would be far too
>> complex I feel.
>>
>> Instead, it would be nice to have a mechanism in the interface to set
>> a "Upstream version is" value for each package if euscan can't tell.
>>
>> Ie:
>>
>> http://euscan.iksaif.net/package/dev-perl/HTML-TreeBuilder-LibXML/
>>
>> Upstream is 0.71 , portage is ( normalised ) to 0.710.0 , and these
>> are in fact the same version. So in 0.710.0 , it would be nice to be
>> able to set the upstream version manually to 0.71 so that euscan no
>> longer reported it as outdated.
>
> I think we could actually handle perl pretty easily. I believe euscan
> will start using CPAN API to check the package versions, and we can
> embed the normalization there.

It's already the case:
https://github.com/iksaif/euscan/blob/master/pym/euscan/handlers/cpan.py
but my mangling functions are probably broken in some cases. If
somebody with a better knowledge of CPAN versionning scheme could fix
them it would be great !

Thanks,