From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/5] eudev: new package.
Date: Mon, 18 Nov 2013 09:46:14 +0100 [thread overview]
Message-ID: <20131118084612.GA13924@pc-eric> (raw)
In-Reply-To: <CAAXf6LWoRXOwzG2RaNSZc+EN4Ev7bJx_hrsgXFuD1Fa5hs8OjA@mail.gmail.com>
Hi!
On Sun, Nov 17, 2013 at 09:16:26AM +0100, Thomas De Schampheleire wrote:
> As making the difference between 'does the package itself also needs
> this dependency' or 'only the package dependencies have this
> dependency' is not obvious, having different rules in this matter
> creates a difficult to maintain situation IMO. Therefore, I am more in
> favor of duplicating the dependencies consistently, along with the
> comments.
Thanks for clarifying. I'll duplicate the dependencies and the comments
in the next series.
next prev parent reply other threads:[~2013-11-18 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 15:34 [Buildroot] [PATCH v3 0/5] udev is now provided by systemd or eudev Eric Le Bihan
2013-11-06 15:34 ` [Buildroot] [PATCH v3 1/5] system: move init system option above /dev management Eric Le Bihan
2013-11-11 0:29 ` Peter Korsgaard
2013-11-06 15:34 ` [Buildroot] [PATCH v3 2/5] sysvinit: depend on SysV selected as init system Eric Le Bihan
2013-11-13 21:37 ` Thomas Petazzoni
2013-11-06 15:34 ` [Buildroot] [PATCH v3 3/5] eudev: new package Eric Le Bihan
2013-11-13 22:41 ` Thomas Petazzoni
2013-11-17 8:16 ` Thomas De Schampheleire
2013-11-17 8:19 ` Peter Korsgaard
2013-11-18 8:46 ` Eric Le Bihan [this message]
2013-11-18 15:02 ` Eric Le Bihan
2013-11-18 23:19 ` Arnout Vandecappelle
2013-11-06 15:34 ` [Buildroot] [PATCH v3 4/5] udev: convert to virtual package Eric Le Bihan
2013-11-06 15:34 ` [Buildroot] [PATCH v3 5/5] systemd: bump to v207 Eric Le Bihan
2013-11-06 15:42 ` [Buildroot] [PATCH v3 0/5] udev is now provided by systemd or eudev Eric Le Bihan
2013-11-13 23:53 ` Thomas Petazzoni
2013-11-15 19:54 ` Eric Le Bihan
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=20131118084612.GA13924@pc-eric \
--to=eric.le.bihan.dev@free.fr \
--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