Re: [Gnu-arch-users] BUG: feature request: 'tla chmod' which 'touch'es files

[Jason McCarty]

Zenaan Harkness wrote:
> Isn't --link kind of mutually exclusive with "desired shared revlib
> perms"?
> 
> To my newbie mind it only really makes sense to disable --link on shared
> revlibs. Don't know how one could determine that though... revlib
> meta-data?

My thought is that to make shared revlibs work, all files in the revlib
would be chmod 444 (555 for dirs and executables), and tla would set the
permissions from recorded meta-data when it built a tree.

But if you want to use --link on such a revlib, a link-breaking editor
is no longer sufficient. You need a new "tla edit" command or similar,
which would break the link and set the permissions of the new file to
those recorded in the meta-data.

The way to go on this depends on how much shared revlibs are valued
versus ease of working with a hard-linked tree (the current problem of
permission changes not being detected is just a fixable bug, and
shouldn't enter into consideration on this issue, IMO). Certainly a
per-revlib flag could be added to let the user decide, but that also
ramps up the learning curve ;-)

-- 
Jason McCarty <address@hidden>