From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH RFC v2] dhcp: package /var/lib/dhcp with dhcp-client rather than dhcp-server
Date: Thu, 12 Jan 2012 12:47:32 -0800 [thread overview]
Message-ID: <4F0F46E4.1040208@linux.intel.com> (raw)
In-Reply-To: <CAGDS+nm7EhwZUxJBiTkGa3x5R71effKqH29J2RzO81ff_kE7Rg@mail.gmail.com>
On 01/11/2012 11:00 AM, Steve Sakoman wrote:
> On Sat, Jan 7, 2012 at 5:14 AM, Eric Bénard<eric@eukrea.com> wrote:
>> Hi,
>>
>> Le Fri, 6 Jan 2012 20:51:54 -0800,
>> Steve Sakoman<steve@sakoman.com> a écrit :
>>> -FILES_dhcp-server = "${sbindir}/dhcpd ${sysconfdir}/init.d/dhcp-server ${localstatedir}/lib/dhcp/"
>>> +FILES_dhcp-server = "${sbindir}/dhcpd ${sysconfdir}/init.d/dhcp-server"
>>
>> isn't this directory necessary for dhcp-server ?
>
> Sorry for the delay in responding! I missed seeing your comment.
>
> Yes, both packages need this directory. But the dhcp-server package
> init already creates it if it doesn't exist:
>
You can still have it in the dhcp-server Package as long as the
attributes (ownership, perm, ...) are the same and it's not a symlink,
so please include it with the FILES-dhcp-server.
Sau!
> case "$1" in
> start)
> echo -n "Starting DHCP server: "
> test -d /var/lib/dhcp/ || mkdir -p /var/lib/dhcp/
>
> So it should be no issue moving the /var/lib/dhcp FILE spec to the
> dhcp-client package.
>
> Steve
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-01-12 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 4:51 [PATCH RFC v2] dhcp: package /var/lib/dhcp with dhcp-client rather than dhcp-server Steve Sakoman
2012-01-07 10:44 ` Otavio Salvador
2012-01-07 13:14 ` Eric Bénard
2012-01-11 19:00 ` Steve Sakoman
2012-01-12 20:47 ` Saul Wold [this message]
2012-01-12 21:56 ` Steve Sakoman
2012-01-16 5:36 ` Saul Wold
2012-01-16 12:30 ` Richard Purdie
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=4F0F46E4.1040208@linux.intel.com \
--to=sgw@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.