From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add more options to eudev package.
Date: Wed, 21 Oct 2015 22:00:35 +0200 [thread overview]
Message-ID: <5627EEE3.3010302@mind.be> (raw)
In-Reply-To: <20151021212450.1c6fc5b4@free-electrons.com>
On 21-10-15 21:24, Thomas Petazzoni wrote:
> Hello David,
>
> On Wed, 21 Oct 2015 13:50:17 +0200, David Kosir wrote:
>
>> I've tried to make second patch better, but realized that it is more
>> complicated than I thought.
>> Best solution I came with to add --libdir=/lib to EUDEV_CONF_OPTS
>> I see that we already specify --libexecdir=/lib
>> That option would allow to use separate /usr, at least to start udev
>> normaly at boot, before /usr is mounted.
>> I think that is good option as it would not break anything (at least
>> what I see).
>> Do you have better idea?
>
> While I understand what you are trying to do, I am not sure we can
> support this in Buildroot upstream. You want eudev to be in / and
> not /usr, but maybe the next person will want this other package to be
> in / and not /usr. How do we handle this ? Add one more option to all
> packages ? Doesn't seem really maintainable.
Actually, it makes sense to me to install it completely in / instead of /usr -
that would also remove the need to have all the --libdir etc. options that we
currently pass. The way it's currently done, eudev's install anyway adds
symlinks back from /lib/libudev.so to /usr/lib/libudev.so.
Of course, includes and pkgconfig still have to be put in /usr.
Regards,
Arnout
>
> I don't really have a good suggestion on how to solve this problem, but
> I'm pretty sure that adding an option to the eudev package is the right
> solution.
>
> Best regards,
>
> Thomas
>
--
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
next prev parent reply other threads:[~2015-10-21 20:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 18:44 [Buildroot] [PATCH 1/1] Add more options to eudev package David Kosir
2015-10-20 20:33 ` Yann E. MORIN
2015-10-20 21:50 ` David Kosir
2015-10-21 11:42 ` David Kosir
2015-10-21 11:50 ` David Kosir
2015-10-21 19:24 ` Thomas Petazzoni
2015-10-21 20:00 ` Arnout Vandecappelle [this message]
2015-10-21 20:18 ` Thomas Petazzoni
2015-10-21 20:39 ` Arnout Vandecappelle
2015-10-22 6:53 ` David Kosir
2015-10-22 7:51 ` Arnout Vandecappelle
2015-10-21 19:37 ` Arnout Vandecappelle
2015-12-20 14:15 ` 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=5627EEE3.3010302@mind.be \
--to=arnout@mind.be \
--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