From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add more options to eudev package.
Date: Thu, 22 Oct 2015 09:51:29 +0200 [thread overview]
Message-ID: <56289581.5000604@mind.be> (raw)
In-Reply-To: <CAOcYpt2UguFUJAufrM8A5O3NwS6u+ogGYkSYf+=QO+tL5TbJjQ@mail.gmail.com>
On 22-10-15 08:53, David Kosir wrote:
>>> 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 ?
>>
>> Because eudev is already installed mostly in / - as I said, even if libudev.so
>> is installed in /usr/lib, there's still a symlink created to point to it from
>> /lib. Same for udevadm: installed in /usr/bin but a symlink is created from
>> /bin. Basically, it's eudev itself that decides it should be in / in addition to
>> /usr.
>
> Exactly, you can check in src/libudevMakefile, install-exec-hook.
>
>> This patch looks good, but was not sent properly and did not appear in our
>> patch tracking system. Can you resubmit properly, using git send-email?
>
> I will try it. I just copy-pasted in into gmail as send-mail was
> complaining about something regarding ssl. I guess that is why it
> didn't work.
'git help send-email' gives a very good explanation about how to configure gmail.
Regards,
Arnout
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . 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-22 7:51 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
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 [this message]
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=56289581.5000604@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