[gobolinux-users] Solution for situation when more programs provide same file

[Isaac Dupree]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hisham.hm at gmail.com wrote:
>> (If conflicts include multiple versions of the same program, this might
>> get ugly...)
> 
> No, they don't. Different versions are expected to often provide the
> same file, so one overwriting the other is not considered a conflict,
> but an upgrade/downgrade.

That makes sense... for the existing behavior of "conflicts".  Does it
solve the problem at the beginning of the thread: you find a broken link
and want to replace it with a working one.  For that purpose, would it
be important to have links to other versions of the symlinked program
(or multiple versions of _each_ alternative) in case they still have
such a file?  I guess that would depend on the intended strategy...
also, all possible files can always be found by looking in
/Programs/*/*/dirname/ regardless (may be inefficient, but never out of
date, of course -- also, the proposed conflict-based symlinks probably
would tell which few /Programs/name directories need to be searched at all).

> This gets me thinking that this whole discussion would
> benefit by being backed with numbers. I wonder how many conflicts
> there are in real-world systems and which they are.

Good question.  A conflict is announced when two different programs are
Symlinked in order, that both have the same file... It is sort of a
conflict for any non-directory /Programs/name/version/**
for any two files that have the same path (the whole ** part), are in a
subdirectory that would be symlinked, and with different program "name".
 Active conflicts are the subset of those where "version" is only
"Current".  Does that seem about right?  I think I can find all those
conflicts on my system with some scripting-fu :)

Isaac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGiTIRHgcxvIWYTTURApveAKCsrARPzHzqp0VIxzNte7cq/5H0lACfUhDe
a62yKTLBnM4xzRkTiE0gw7g=
=mIjV
-----END PGP SIGNATURE-----