| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp updates - more permissions tweaking |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Thu, 25 Jul 2013 13:33:17 +1000 |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <223462914.2084329.1374715690313.JavaMail.root@xxxxxxxxxx> |
| References: | <51F0732C.30009@xxxxxxxxxxxxxxxx> <223462914.2084329.1374715690313.JavaMail.root@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 |
On 25/07/13 11:28, Nathan Scott wrote: ... Can you give a 5 second intro to how this file (qa/src/permslist) works? Lemme try ...OK, I should probably re-engineer this ... permslist is built by mkpermslist in the same qa dir ... it needs the source tree to grab the $(INSTALL) lines from the makefiles, but then I expand the PCP_FOO vars in mkpermslist ... I'll stop doing the expansion, and move that to QA 994, which will fix your path differences. The optional part is added in mkpermslist for those $(INSTALL) lines that are covered by conditional gmake goo, and as thus the artifact may, or may not, be in the package (like pmwebd's log) and/or created at run time (like /var/run/pcp for Debian) ... this is hard-coded knowledge in mkpermslist as it cannot be deduced from the $(INSTALL) lines. Does that help? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Unusual test failures, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] pcp updates - more permissions tweaking, Nathan Scott |
| Previous by Thread: | Re: [pcp] pcp updates - more permissions tweaking, Nathan Scott |
| Next by Thread: | Re: [pcp] pcp updates - more permissions tweaking, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |