Shadow directory - Private file location
TL
specified location. As I understand it, the private files are
currently located in a subdirectory of the public file. This puts the
private files within the project's public directory structure. Since
the private files are used only by one person, why not put them in a
subdirectory of that user's .Leo file?
Edward K. Ream
Because of name conflicts.
Edward
Kent Tenney
+1
Also would allow opening a @shadow file from a location where
I don't have permission to create the shadow directory.
> >
>
Terry Brown
"Edward K. Ream" <edre...@gmail.com> wrote:
> Since
> > the private files are used only by one person, why not put them in a
> > subdirectory of that user's .Leo file?
>
> Because of name conflicts.
I guess I don't see having them in the "public" directory as that much
of an issue. Is it really a public directory, or just your local copy
of the public directory? It probably has .o or .pyc or ~ files in it
that aren't to be shared either - that's what .bzrignore does(*).
BUT - I guess you could get around the problem of storing them in one
place by naming them something like:
main.c-LS2341 where you force the LS2341 part to be unique.
Not convinced it's worth it myself.
Cheers -Terry
(*) As if there are no workflows that don't involve bzr :)
Edward K. Ream
I am convinced of the reverse. The naming convention creates a time bomb: a potential problem that almost never happens, and causes grief and confusion when it does happen. In essence, any naming convention creates *yet another* association between files. We already have a 3-way association between @shadow node and public and private files. To try to disambiguate files with the same name creates an association between one (of possibly several) @shadow node and the corresponding files. This is surprisingly complex, and potentially nasty.
I don't believe .leo_shadow directories, on a *private* machine, ignored in .bzrignore, create any significant problem.
Edward
Terry Brown
"Edward K. Ream" <edre...@gmail.com> wrote:
> > Not convinced it's worth it myself.
>
> I am convinced of the reverse.
[snip]
> I don't believe .leo_shadow directories, on a *private* machine,
> ignored in .bzrignore, create any significant problem.
Um, right, that was my point... I think you could move the .leo_shadow
dir if there was a really compelling reason to do so, but I'm
"Not convinced it's worth it myself." :-)
Cheers -Terry