On Thu, Feb 2, 2012 at 12:53, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> Agreed, mkdir is much more likely to be available than install on most
> target machines.
>
I did it and pushed to my tree.
When changing it, I bumped PR again as I had it merged in our local tree to
fix
On Thu, 2012-02-02 at 10:43 +, Phil Blundell wrote:
> On Wed, 2012-02-01 at 19:01 -0200, Otavio Salvador wrote:
> > On Wed, Feb 1, 2012 at 18:57, Phil Blundell wrote:
> > On Wed, 2012-02-01 at 20:27 +, Otavio Salvador wrote:
> > > pkg_postinst_dhcp-server() {
> > >
On Wed, 2012-02-01 at 19:01 -0200, Otavio Salvador wrote:
> On Wed, Feb 1, 2012 at 18:57, Phil Blundell wrote:
> On Wed, 2012-02-01 at 20:27 +, Otavio Salvador wrote:
> > pkg_postinst_dhcp-server() {
> > +install -d $D/${localstatedir}/lib/dhcp
>
>
On Wed, Feb 1, 2012 at 18:57, Phil Blundell wrote:
> On Wed, 2012-02-01 at 20:27 +, Otavio Salvador wrote:
> > pkg_postinst_dhcp-server() {
> > +install -d $D/${localstatedir}/lib/dhcp
>
> Is "install" guaranteed to be available on the target? I would have
> thought "mkdir -p" would be
On Wed, 2012-02-01 at 20:27 +, Otavio Salvador wrote:
> pkg_postinst_dhcp-server() {
> +install -d $D/${localstatedir}/lib/dhcp
Is "install" guaranteed to be available on the target? I would have
thought "mkdir -p" would be better.
p.
___
O
Both server and client needs access to leases files so its creation
and removal are now handled by postinst/postrm scripts.
Signed-off-by: Otavio Salvador
---
meta/recipes-connectivity/dhcp/dhcp.inc | 19 ++-
meta/recipes-connectivity/dhcp/dhcp_4.2.0.bb |2 +-
2 files
