From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] dhcp: Update to 4.2.3-P2
Date: Wed, 8 Feb 2012 11:31:16 -0500 [thread overview]
Message-ID: <4F32A354.4030107@windriver.com> (raw)
In-Reply-To: <1328717410.14363.46.camel@phil-desktop>
On 2/8/12 11:10 AM, Phil Blundell wrote:
> On Wed, 2012-02-08 at 18:06 +0200, Andrei Gherzan wrote:
>> 1. Update to 4.2.3-P2
>> 2. From 4.2.0 final release, -lcrypto check was removed and we compile static libraries
>> from bind that are linked to libcrypto. This is why i added a patch in order to add
>> -lcrypto to LIBS.
>>
>> Signed-off-by: Andrei Gherzan<andrei@gherzan.ro>
>
> [...]
>
>> @@ -66,7 +61,7 @@ FILES_dhcp-server-config = "${sysconfdir}/default/dhcp-server ${sysconfdir}/dhcp
>>
>> FILES_dhcp-relay = "${sbindir}/dhcrelay ${sysconfdir}/init.d/dhcp-relay ${sysconfdir}/default/dhcp-relay"
>>
>> -FILES_dhcp-client = "${base_sbindir}/dhclient ${base_sbindir}/dhclient-script ${sysconfdir}/dhcp/dhclient.conf"
>> +FILES_dhcp-client = "${sbindir}/dhclient ${base_sbindir}/dhclient-script ${sysconfdir}/dhcp/dhclient.conf"
>> RDEPENDS_dhcp-client = "bash"
>>
>> FILES_dhcp-omshell = "${bindir}/omshell"
>
> This isn't just a straightforward update, you seem to be moving dhclient
> from ${base_sbindir} to ${sbindir}. If that's a good thing (which
> doesn't seem totally obvious to me) then it ought at least to be
> mentioned in the commit message.
I believe that dhcp-client was in the base_sbindir specifically to enable early
boot/network setup before /usr is potentially available. I think this is still
desired.
--Mark
> p.
>
>
>
> _______________________________________________
> 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-02-08 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 16:06 [PATCH] dhcp: Update to 4.2.3-P2 Andrei Gherzan
2012-02-08 16:10 ` Phil Blundell
2012-02-08 16:30 ` Otavio Salvador
2012-02-08 17:00 ` Phil Blundell
2012-02-08 18:40 ` Andrei Gherzan
2012-02-08 18:46 ` Otavio Salvador
2012-02-08 19:00 ` Andrei Gherzan
2012-02-08 22:20 ` Andrei Gherzan
2012-02-08 22:28 ` Khem Raj
2012-02-08 16:31 ` Mark Hatle [this message]
2012-02-08 16:36 ` Andrei Gherzan
2012-02-24 18:27 ` Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2012-02-07 21:27 Andrei Gherzan
2012-02-02 16:20 Andrei Gherzan
2012-02-02 18:32 ` Otavio Salvador
2012-02-02 20:24 ` Andrei Gherzan
2012-02-02 22:07 ` Andrei Gherzan
2012-02-03 10:43 ` Otavio Salvador
2012-02-07 16:20 ` Saul Wold
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=4F32A354.4030107@windriver.com \
--to=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox