On Tue, 26 Jun 2018 18:58:42 +0200, Andy Goth <andrew.m.g...@gmail.com>
wrote:
I think the next project that needs this feature should write a utility
script for themselves that uses the uv commands to extract files however
makes sense for them.
well, AFAIAC, I would be happy if fossil would support the equivalent of
this shell one-liner:
for i in $(fossil uv ls); do fossil uv export $i $i; done
(plus, possibly checking whether there is any need to extract the file(s)
again (local copy more recent or older than time stamp in the
`unversioned' table?).
as explained previously, the use case in mind primarily would be a project
where all uv-files reside somewhere within the checkout.
as an aside: it is really very nice that `fossil uv export' silently
creates missing target directories (recursively, too) i.e. does something
like `mkdir -p' implicitly. so the shell command above works even in a
pristine clone.
but doing it via shell commands remains a hack/workaround. fossil
providing functionality to treat uv-files and tracked files mostly on
equal footing during ci/co/up/push/pull/sync (considering, of course, that
there is no history/no deltas for uv-files) would be much better.
if that collides with the original intent of `uv' (and support of uv-files
_outside_ of the checkout dir is crucial -- so that it might not be always
a good idea to "flood" the file system at random places with copies of the
uv-files), one or two settings controlling the behavior of `uv' related
stuff still would be possible. in principle at least...
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
