28 Mar
2012
28 Mar
'12
2:11 p.m.
Am 28. März 2012 05:42 schrieb David Robillard <d(a)drobilla.net>et>:
The point here is to make it as simple and as little fault-prone to the user
as possible:
A user should be able - with a single button-click (or cml) - to make
a directory with all files belonging to a session, optionally either
keeping references or creating copies of them (of Lfiles).
Did you ever re-assign 200 symlinks ?
Compare that with a simple search-and-replace in a textfile, with an
editor of your choice.
--
E.R.
On Tue, 2012-03-27 at 14:24 +0200, Emanuel Rumpf
wrote:
I am having a hard time imagining anything *less* likely to be adopted
than trying to cram a *database* down everyone's throats to save some
files! ;)
With database here, actually, I'm refering to a more or less simple text
format.
for example, recently I stumbled about: GNU recutils
(readable, but it is slow)
No session manager that forces everyone to use some database would ever
fly. This is obvious.
It doesn't force the clients to use a db. The SM would have a text-db and
simply communicated with the clients, to find out their files-in-use.
- having
symlinks leaves the user with the question how to reliably
copy a directory, without messing up everything (dereference yes/no,
follow links yes/no ...), something that is critical to deside
That is inherent to any solution with "links" to external resources.
Links to external resources are a requirement. If you want to move a
session, use a smart tool that can fix the links, or archive it.