[Scons-users] --dry-run can still remove files - is this a bug?

[chris warth]

Thanks for looking it over.   'source' never lived in the current
directory.  It is the result of an earlier computation that deposited it
into 'output/'.   Now I want to perform an additional analysis step on the
results that were deposited in the 'output/' directory.    I have had to
simplify this problem to the bare minimum from a much larger pipeline I
inherited.

I guess we'll have to disagree.  To me there is no nuance or shades of grey
in this.  In my opinion --dry-run should not modify any file, period.
There's always the pathological case of me adding code that intentionally
modifies the filesystem in the process of building tree, but I don't think
we're talking about that here.

- Chris





On Wed, Aug 5, 2015 at 12:05 PM, Bill Deegan <bill at baddogconsulting.com>
wrote:

> Chris,
>
> I don't think this is a bug.
> You're asking SCons to make 'output' a variant dir of the current dir, and
> them you've removed  source.txt from the current dir, and then run scons
> which removes the output dir copy?
>
> -Bill
>
> On Wed, Aug 5, 2015 at 11:53 AM, chris warth <cswarth at gmail.com> wrote:
>
>> Thanks for the reply a task trace is available here -
>> http://pastebin.com/jhW2dMZk
>>
>>
>>>
>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-users at scons.org
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>>
>
> _______________________________________________
> 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/20150805/4c0ed16f/attachment-0001.html>