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

[Arnout Vandecappelle <arnout@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.

> 
> 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