From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] systemd: Fix packaging warnings and spin libnss_myhostname to package of its own
Date: Sat, 16 Feb 2013 13:05:44 +0100 [thread overview]
Message-ID: <lyd2w0mpk7.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CAJTo0LY7zkGkAc4XR_7yp1R-=WZbRA=M7xoo9EiYMpYjGkOaTw@mail.gmail.com> (Ross Burton's message of "Fri, 15 Feb 2013 20:33:23 +0000")
"Burton, Ross" <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:
> On 15 February 2013 19:29, Khem Raj <raj.khem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> + /lib/udev/hwdb.d \
>
> Would this obsolete the patch I posted earlier to add pci/usb IDs?
no; these files are useless without an 'udevadm hwdb --update' in a
script.
I did not looked at the generated database, but the hwdb.d files are
large (4 MiB) so that they should be moved into an own subpackage.
Enrico
prev parent reply other threads:[~2013-02-16 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 19:29 [PATCH] systemd: Fix packaging warnings and spin libnss_myhostname to package of its own Khem Raj
2013-02-15 20:33 ` Burton, Ross
2013-02-16 12:05 ` Enrico Scholz [this message]
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=lyd2w0mpk7.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
/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