From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 21 Oct 2015 22:18:04 +0200 Subject: [Buildroot] [PATCH 1/1] Add more options to eudev package. In-Reply-To: <5627EEE3.3010302@mind.be> References: <20151020203326.GA31310@free.fr> <20151021212450.1c6fc5b4@free-electrons.com> <5627EEE3.3010302@mind.be> Message-ID: <20151021221804.483ac95d@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Wed, 21 Oct 2015 22:00:35 +0200, Arnout Vandecappelle wrote: > > 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. If we install it unconditionally in /, then it's fine with me. What I would dislike is to start having options for such things. However, there is still the question: why eudev in /, and not any other package that other users may find important to have in / ? Where do we put the boundary ? Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com