From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Add missing config to RPM target package
Date: Mon, 31 Aug 2015 16:32:23 +0200 [thread overview]
Message-ID: <20150831163223.67982cd3@free-electrons.com> (raw)
In-Reply-To: <55DCC1F6.4060008@gmx.de>
Dear Andreas Ehmanns,
On Tue, 25 Aug 2015 21:28:54 +0200, Andreas Ehmanns wrote:
> in my first try I had no pcre support, so rpm package was built with
> --with-pcre=none
> Trying to install a binary rpm just containing one file on my target
> system failed at the very beginning when rpm was checking package
> dependencies. Setting --with-pcre=internal solved this problem. So it
> seems to me that pcre is necessary to to dependency checks which is in
> my opinion one of the main features or rpm. Isn't it?
If that's indeed the case, then pcre support is really mandatory for
RPM to be useful. Therefore, can you send a patch to make the pcre
dependency a mandatory one? Don't forget to add a comment explaining
why we're making it mandatory even if RPM makes it an optional
dependency.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-31 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 11:26 [Buildroot] Add missing config to RPM target package universe II
2015-08-21 13:41 ` Vicente Olivert Riera
2015-08-24 16:25 ` universe II
2015-08-25 9:38 ` Vicente Olivert Riera
2015-08-25 19:14 ` Andreas Ehmanns
2015-08-23 18:06 ` Thomas Petazzoni
2015-08-25 19:28 ` Andreas Ehmanns
2015-08-31 14:32 ` Thomas Petazzoni [this message]
[not found] ` <55E89D2B.4090804@gmx.de>
2015-12-04 7:30 ` Andreas Ehmanns
2015-12-04 8:13 ` Thomas Petazzoni
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=20150831163223.67982cd3@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