On Aug 1, 2016 8:02 PM, "Ron W" <ronw.m...@gmail.com> wrote:
>
> On Mon, Aug 1, 2016 at 8:22 PM, Adam Jensen <han...@riseup.net> wrote:
>>
>> On 08/01/2016 07:40 PM, bch wrote:
>>
>> > in a controlling file. Something like a purpose-built makefile or
>> > script that handles this layout, so that -it- can be versioned in
>> > fossil; fossil wasn't/isn't currently designed to handle that sort of
>> > metadata - which *arguably* should be handled in a script as described
>> > above. Fossil can then handle that script as an artifact.
>> >
>>
>> Is there a way to run these scripts automatically after each checkout?
>
>
> My team and I do this as part of the build procedure. Basically, we treat
those as part of the "product" being built, so when we do a "clean check
out", the first run of make will create those directories. We don't need
them before that.
>
This is indeed the process I would have described. Fossil isn't doing any
*work* with respect to your project - it's just laying out tools +
resources. It's unfortunate that empty directories are a cause for
confusion, but if you accept that and work as Ron's team does, think of
fossil as managing the *content* of files (and limited meta data), and
consider that things like ownership, permissions, empty directories (and
perhaps more) are the responsibility of the project and it's tooling
(build/setup). And to clear what I think might be a small amount of
confusion, when I was talking about executable bits and --x, I was using
those 3 characters ("--x") to stand in for UNIX permissions like rwx - not
as a double-dash switch.
Regards,
-bch
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
