From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package/python-rtslib-fb: bump version to 2.1.58
Date: Fri, 7 Oct 2016 23:30:08 +0200 [thread overview]
Message-ID: <20161007233008.391cde28@free-electrons.com> (raw)
In-Reply-To: <20161007231043.39e1d100@trantor>
Hello,
On Fri, 7 Oct 2016 23:10:43 +0200, Christophe Vu-Brugier wrote:
> > Buildroot's policy is to follow what upstream decides... even if you
> > don't like it :)
>
> I understand Buildroot's policy.
>
> The new dependencies are required by new features (user backstores rely
> on dbus) or brought to improve the code and its stability (pyudev). I
> am perfectly OK with this focus on features and stability.
>
> And as the same time, as a buildroot user, I like when my rootfs is
> small :) Let's call this "Embedded Schizophrenia".
Well, nothing prevents you from complaining to the upstream developers,
and ask them to make those new dependencies optional.
> Sorry, I was not clear. I think it would be better to revert Bernd's
> patch. I can cook up patches to:
>
> * clarify that rtslib-fb should be fetched from GitHub instead of PyPI
> * clarify that rtslib-fb, configshell-fb and targetcli-fb should be
> kept in sync.
> * later upgrade the three packages.
>
> Would that be OK for Bernd and you?
Makes sense to me. I'll revert Bernd's patch.
Thanks for your feedback!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-07 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 13:15 [Buildroot] [git commit] package/python-rtslib-fb: bump version to 2.1.58 Thomas Petazzoni
2016-10-07 16:16 ` Christophe Vu-Brugier
2016-10-07 16:19 ` Christophe Vu-Brugier
2016-10-07 20:26 ` Thomas Petazzoni
2016-10-07 21:10 ` Christophe Vu-Brugier
2016-10-07 21:30 ` Thomas Petazzoni [this message]
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=20161007233008.391cde28@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