[Scons-users] Customize build decision logic for phony targets, that doesn't involve files

[Bill Deegan]

You can use the following command to retrieve the SHA hash from a remote
repo's HEAD (or any branch)
git ls-remote upstream HEAD
ec7f4638d02bdfe31313ddef8a63ece2ee22932f    HEAD

How big are the LXC containers?
Is this like docker where it's composed of overlay file systems?
-Bill

On Sun, Mar 27, 2016 at 11:15 AM, Bill Deegan <bill at baddogconsulting.com>
wrote:

> The target is he lxc container, which has a hash id right?
> The source is the git repo, potentially the hash for the newest commit?
>
> So you do have source/targets.
> The trick is getting SCons to use those..
>
> -Bill
>
> On Sun, Mar 27, 2016 at 3:55 AM, Andrew Pashkin <andrew.pashkin at gmx.co.uk>
> wrote:
>
>> On 03/16/2016 05:56 AM, Bill Deegan wrote:
>>
>>> Anyway if your builder doesn't read or write any files, perhaps you can
>>> explain exactly what it does do?
>>> What causes it to rebuild? What's the contents/source of the abstract
>>> value?
>>>
>>> That may help to provide a solution.
>>>
>> It builds an LXC container and I want SCons to re-build it when a git
>> repository, with sources of some program, updates.
>>
>> _______________________________________________
>> 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/20160328/8ea27a15/attachment.html>