[Scons-users] detecting invalid command actions

[Tom Tanner (BLOOMBERG/ LONDON)]

well, it's quite a longish function I have to patch. I'll have to see if I can patch a setter or getter to get the same effect.

From: bill at baddogconsulting.com At: Feb 25 2015 18:47:05
To: Tom Tanner (BLOOMBERG/ LONDON), scons-users at scons.org
Subject: Re: [Scons-users] detecting invalid command actions

Tom,

Can't you monkey patch that in, if that's something you always want to have and void the need to patch the sources?
Barring that, maintain your own branch and merge the releases into it via mercurial?

-Bill

On Wed, Feb 25, 2015 at 9:57 AM, Tom Tanner (BLOOMBERG/ LONDON) <ttanner2 at bloomberg.net> wrote:

we have a check currently in our scons which checks that executor.get_contents() doesn't contain an absolute path to a users git clone, as this rather destroys the caching.

This isn't very satisfactory though, obviously, because it's a change that has to be merged whenever we get a new scons.

Is there some more portable way I can attach a check to every action to ensure they don't have inappropriate absolute paths lurking?
_______________________________________________
Scons-users mailing list
Scons-users at scons.org
https://pairlist4.pair.net/mailman/listinfo/scons-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20150226/20ef37c1/attachment.html>