From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-can: bump to 1.4.1
Date: Sat, 2 Jan 2016 23:31:27 +0100 [thread overview]
Message-ID: <20160102233127.0c6f078c@free-electrons.com> (raw)
In-Reply-To: <20160101222835.GD2182@free.fr>
Yann, all,
On Fri, 1 Jan 2016 23:28:35 +0100, Yann E. MORIN wrote:
> I think we want to use upstream locations as much as possible, and only
> fallback to alternative locations when there is no upstream, or upstream
> is flaky.
For Python packages, I actually find it quite practical when PyPi is
used. Indeed, instead of having dozens of weird upstream locations and
release behavior, you have one consistent way of fetching Python
modules. It also makes it easier when reviewing new packages, when
looking at package bumps, since you know what to expect from PyPi.
So I wouldn't be as strict as you said in terms of not using PyPi.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-02 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 22:18 [Buildroot] [PATCH] python-can: bump to 1.4.1 Yegor Yefremov
2016-01-01 22:28 ` Yann E. MORIN
2016-01-01 22:49 ` Yann E. MORIN
2016-01-02 9:05 ` Yegor Yefremov
2016-01-02 11:15 ` Yann E. MORIN
2016-01-02 21:04 ` Arnout Vandecappelle
2016-01-02 21:50 ` Angelo Compagnucci
2016-01-03 22:24 ` Arnout Vandecappelle
2016-01-04 8:54 ` Yegor Yefremov
2016-01-13 14:26 ` Yegor Yefremov
2016-01-02 22:31 ` Thomas Petazzoni [this message]
2016-01-03 20:50 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160102233127.0c6f078c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox