[Buildroot] [PATCH] python-can: bump to 1.4.1

Angelo Compagnucci angelo.compagnucci at gmail.com
Sat Jan 2 21:50:44 UTC 2016


Yegor, Arnout, All

2016-01-02 22:04 GMT+01:00 Arnout Vandecappelle <arnout at mind.be>:
> On 02-01-16 12:15, Yann E. MORIN wrote:
>> Yegor, All,
>>
>
> [snip]
>
>> Still, I think we should use upstream locations, not some packaging
>> location. For example, switching to PyPi for Python packages would be
>> like switching to Debian for 'native' packages. We don't do that (except
>> when upstream has disapeared, is acting...)
>
>  This analogy is not quite correct. PyPi is a distribution channel, not a
> downstream. Not that I can think of a better analogy though. But the important
> thing is: the PyPi location is under control of the upstream author, so it is
> equally upstream as the git repo. Brian Thorne (the python-can author) doesn't
> upload tarballs to the bitbucket location (you only get the automatic ones), but
> only to PyPi. So there really is something to be said for using PyPi as the
> download location.

I'm following (and contributing to) python-can for more than a year
now and this is the first time in my memory that a release was
uploaded to PyPi, and this happened cause someone asked for that on a
project issue.

IMHO, it will not happen in the future again if not prompted by someone.

Indeed, I originally submitted the package using bitbucket as a source
location, cause it was the only available.

Sincerely, Angelo.

>
>>
>> The argument about the hash is only patially valid: md5 is long dead
>> now, and you still have to compute a sha256 anyway.
>
>  Very true.
>
>  Basically I'm OK with either location.
>
>  Regards,
>  Arnout
>
>>
>> But as seen on IRC: let's see what others think.
>>
>> Regards,
>> Yann E. MORIN.
>>
>
>
> --
> Arnout Vandecappelle                          arnout at mind be
> Senior Embedded Software Architect            +32-16-286500
> Essensium/Mind                                http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot



-- 
Profile: http://it.linkedin.com/in/compagnucciangelo


More information about the buildroot mailing list