Re: [LEDE-DEV] Makefile question

2017-02-14 Thread Yousong Zhou
On 15 February 2017 at 06:33, Philip Prindeville wrote: [...] >>> >>> Part of the problem is making package/Makefile recurse with additional >>> arguments and a different working directory… When I try to do this, the >>> submake of package/Makefile gets

Re: [LEDE-DEV] Makefile question

2017-02-14 Thread Philip Prindeville
> On Feb 13, 2017, at 11:25 PM, Yousong Zhou wrote: > > On 14 February 2017 at 10:51, Philip Prindeville > wrote: >> >> Hi Yousong, >> >> I’ve been working on both OpenWRT and LEDE and needed to get some hooks >> working in OpenWRT

Re: [LEDE-DEV] Makefile question

2017-02-14 Thread Milan Kočvara
I did it this way I have own script (/etc/rc.local_once) where I do, what I need after first boot and place it to $ENV/files/etc <- for example It is started from /etc/rc.local For sure, is started only once "after first boot", last row of this script empties default file /etc/rc.local (I

Re: [LEDE-DEV] Makefile question

2017-02-13 Thread Yousong Zhou
On 14 February 2017 at 10:51, Philip Prindeville wrote: > >> On Feb 12, 2017, at 10:04 PM, Yousong Zhou wrote: >> >> On 13 February 2017 at 11:23, Philip Prindeville >> wrote: >>> On Feb 11,

Re: [LEDE-DEV] Makefile question

2017-02-12 Thread Philip Prindeville
> On Feb 12, 2017, at 11:20 PM, Philip Prindeville > wrote: > > >> On Feb 12, 2017, at 11:15 PM, David Lang wrote: >> >> On Sun, 12 Feb 2017, Philip Prindeville wrote: >> If you look for where the /files/* are copied into the

Re: [LEDE-DEV] Makefile question

2017-02-12 Thread Philip Prindeville
> On Feb 12, 2017, at 11:15 PM, David Lang wrote: > > On Sun, 12 Feb 2017, Philip Prindeville wrote: > >>> If you look for where the /files/* are copied into the filesystem, that >>> is probably the place you would want to add your scripting hooks. >> >> Good

Re: [LEDE-DEV] Makefile question

2017-02-12 Thread David Lang
On Sun, 12 Feb 2017, Philip Prindeville wrote: If you look for where the /files/* are copied into the filesystem, that is probably the place you would want to add your scripting hooks. Good idea. I’ll look there. Once you find this, may I suggest that you create /scripts/* and contribute

Re: [LEDE-DEV] Makefile question

2017-02-11 Thread David Lang
On Sat, 11 Feb 2017, Philip Prindeville wrote: This can't eliminate the /etc/rc.d/S* files as it only adds files, and it's not as flexibile as adding a user or changing a password (as it would just let you replace the /etc/passwd, /etc/shadow files, not modify them). If you look for where

Re: [LEDE-DEV] Makefile question

2017-02-11 Thread Philip Prindeville
> On Feb 10, 2017, at 10:33 PM, David Lang wrote: > > On Fri, 10 Feb 2017, Philip Prindeville wrote: > >> Hi. >> >> I was wondering if there’s an obvious place to install a hook that’s: >> >> (a) after all the packages have been installed; >> (b) before the root filesystem

Re: [LEDE-DEV] Makefile question

2017-02-11 Thread Hannu Nyman
John Crispin wrote at Fri Feb 10 21:37:19 PST 2017: > jow posted some instructions on how to overload parts of a packages install template using one of buildroots built-in features, but i am failing to find the mail in the archive. You are likely referring to this:

Re: [LEDE-DEV] Makefile question

2017-02-10 Thread John Crispin
On 11/02/2017 06:33, David Lang wrote: > On Fri, 10 Feb 2017, Philip Prindeville wrote: > >> Hi. >> >> I was wondering if there’s an obvious place to install a hook that’s: >> >> (a) after all the packages have been installed; >> (b) before the root filesystem image gets finalized; >> >> I’d

Re: [LEDE-DEV] Makefile question

2017-02-10 Thread David Lang
On Fri, 10 Feb 2017, Philip Prindeville wrote: Hi. I was wondering if there’s an obvious place to install a hook that’s: (a) after all the packages have been installed; (b) before the root filesystem image gets finalized; I’d like to be able to run some simple sed scripts inside the