Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/1] package/rpm: switch to version 4.12.0.1
Date: Sun, 11 Sep 2016 15:54:31 +0200	[thread overview]
Message-ID: <20160911155431.6204c127@free-electrons.com> (raw)
In-Reply-To: <20160909163708.31980-1-james.knight@rockwellcollins.com>

Hello,

On Fri,  9 Sep 2016 12:37:08 -0400, James Knight wrote:
> The provided switches from the RPM5 implementation to rpm.org's stream.
> 
> Signed-off-by: James Knight <james.knight@rockwellcollins.com>

Could you give some details on why the rpm.org version is better than
the rpm5.org version? The motivation to move from a 5.x version to
a 4.x version doesn't look immediately obvious, so some more
details would be good to have.

RPM seems like a weird project, it's widely used, but it's very hard to
understand what is the real upstream for it. This fact was even
discussed on LWN recently: https://lwn.net/Articles/196523/.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-11 13:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 16:37 [Buildroot] [PATCH v5 1/1] package/rpm: switch to version 4.12.0.1 James Knight
2016-09-11 13:54 ` Thomas Petazzoni [this message]
2016-09-11 21:10   ` Arnout Vandecappelle
2016-09-11 21:15     ` Thomas Petazzoni
2016-09-12 16:06       ` James Knight
2016-09-12 19:12         ` Thomas Petazzoni
2016-09-12 20:00           ` James Knight
2016-09-12 20:02         ` Arnout Vandecappelle
2016-09-12 21:33 ` Arnout Vandecappelle
2016-09-12 22:22   ` James Knight
2016-09-13  6:29     ` Arnout Vandecappelle
2016-09-15 15:50     ` James Knight
2016-09-15 21:09       ` Arnout Vandecappelle

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=20160911155431.6204c127@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