pcp
[Top] [All Lists]

Re: [pcp] pcp updates - more permissions tweaking

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pcp updates - more permissions tweaking
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 24 Jul 2013 23:38:07 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <51F09C7D.60803@xxxxxxxxxxxxxxxx>
References: <51F0732C.30009@xxxxxxxxxxxxxxxx> <223462914.2084329.1374715690313.JavaMail.root@xxxxxxxxxx> <51F09C7D.60803@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: ygMpUdee+ZOg2tvsDgZ772YzfxQRaw==
Thread-topic: pcp updates - more permissions tweaking

----- Original Message -----
> 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.

Ah, so that bit needs to be extended for all the tmp dirs (they all use
the same makefile conditional goop - pmlogger, mmv, pmdabash), I think.

> Does that help?
> 

Yes, thanks!

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>