13 Jan
2021
13 Jan
'21
10:11 p.m.
On Wednesday 13 of January 2021 22:54:47 Michael via tde-users wrote:
Ah, cool, thanks for that explanation, I’m sure I
could have pieced it
together, but it’s nice seeing it all in one place.
Completely just curiosity on my part: If the program name is left as
amarok and the TDE version is in /opt/trinity/bin/ would that conflict
with amarok (official/upstream? I’m not sure what that name is suppose
to be.) in /usr/bin? Or what happens when you have both:
/opt/trinity/bin/amarok
/usr/bin/amarok
as being from different packages?
In the current state where Trinity is installed in a separate folder, this
does not cause a file conflict, but it depends on how you run the session.
If you have a full TDE session, then the PATH is set so that the
path /opt/trinity/bin is inserted before /usr/bin, so when you
enter "amarok" (without full patch) the Trinity version will start
=> /opt/trinity/bin/amarok. If you do not have a full TDE session or a
manually modified PATH, then the upstream version will start
=> /usr/bin/amarok.
If we wanted to install in /usr instead of /opt/trinity, then a file
conflict would occur and the user could not have both variants installed.
Therefore, the need to rename binaries and libraries blocks the
possibility of inclusion as a standard part of distributions.
Cheers
--
Slávek