From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lldpd: new package
Date: Mon, 18 Jan 2016 21:13:09 +0100 [thread overview]
Message-ID: <20160118211309.057d1922@free-electrons.com> (raw)
In-Reply-To: <CAHfJR7jVn99vE=6i+Z7D5w6wMPHYyOrYm+1aM-HTvMWq2PeG6w@mail.gmail.com>
Hello Julien,
On Mon, 18 Jan 2016 18:23:35 +0100, Julien Floret wrote:
> > BR2_PACKAGE_LIBEVENT has a "depends on !BR2_bfin" so you need to
> > duplicate this dependency in lldpd's Config.in file.
>
> I don't see such dependency for libevent...
> Maybe you got mixed up with libev?
Absolutely. Blame the auto-completion, or my stupidity. libevent indeed
doesn't have any dependency, so what you did is perfectly fine.
> > Do we really need to allow the configuration of the user and group? We
> > generally don't do this for most package. Also, are _lldpd a good
> > choice? Why the leading underscore?
> >
> > If we're really talking about Unix user/group, then I would suggest to
> > just have an option to enable/disable privilege separation. And when
> > enabled, use lldpd as the user and group names.
> >
> > Also, shouldn't these user and group names be created by Buildroot in
> > the target root filesystem?
> >
>
> _lldpd (with the leading underscore) is the default value of the user and
> group in lldpd, when privsep is enabled but user/group are not specified.
> But I agree this is not really needed.
>
> In fact, for a first simple patch, I suggest to disable explicitely the
> privilege separation feature. We can then handle it properly in a later patch,
> with user and group names created in the target root filesystem.
Sounds good to me.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-18 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 10:14 [Buildroot] [PATCH] lldpd: new package Julien Floret
2016-01-18 15:04 ` Thomas Petazzoni
2016-01-18 17:23 ` Julien Floret
2016-01-18 20:13 ` Thomas Petazzoni [this message]
2016-01-19 11:10 ` [Buildroot] [PATCH v2] " Julien Floret
2016-01-20 22:03 ` 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=20160118211309.057d1922@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