You are here

Add new comment

I wanted to compile your arrangement to test, and above all to use, because I needed it (although not urgently).
I don't know why I didn't get compile. (Linux mysteries)

Then I realized that I could edit Qtractor.conf directly, and I shared the variable in case someone else wanted to configure it that way (without having to recompile Qtractor).

--- Info extra---

"what's this really about?"
There really is an underlying issue. I share it because it is something that I really think needs to be commented on, but of course I am not forcing anyone to read it.
It has nothing to do directly with Qtractor, but Qtractor is affected.

_We have a problem, and it is UNIX mode_
The hierarchical organization of Unix files is a great absurdity, and that causes problems.
I have already commented on these types of problems before in this forum (problems when sharing plugins, problems when creating your own file organization for a custom workflow...).
I knew those problems were there, but I didn't know the origin, I finally realized: UNIX mode.

Dismember the app identity into "bin", "etc", ".config", "share" is not functional.
And worse, it leaves "shared" resources out of reach of the user under administrative permissions. That "share" requires administrative permissions is a paradox in concept.

It makes it difficult and even prevents the user from locating and establishing their own organization.

Due to this nonsense, some programmers choose to save the resources of their programs in the user path in hidden!!! folders, others in the personal documents folder, others in the local .var, o .local or .config folders... Total chaos. (hidden!!!: Hiding doesn't help either.)

There are some initiatives that try to provide a solution:
- Appimages: Hiding the app's resources in a Zip doesn't seem like a solution to me.

- HelloSystem: A FreeBSD distro from the same author of Appimages that recreates Apple's System7 experience. I think it (like System7 and MacOX) have the same problem as Appimages.

- GoboLinux: I think it is a successful proposal, but it is still far from being friendly.

(It is curious that perhaps Windows is the one that has the most accurate and free file organization.
Programs maintain an identity with their resources, their configurations, and are traceable.
User programs are differentiated from system applications.
Installable with a graphical interface that allows you to decide where to install, without conflicting with anything...)

_It's not a complaint, it's just a statement of a problem_
I can't create a Linux distribution that solves all this, I lack knowledge and resources.
I would be at the same point as GoboLinux, I would have to create installables (in my case with a Windows-style graphical interface) for the thousands of existing programs and maintain them. That is a task that requires many people.

What I can do is try to find solutions so that my user's file structure is the least dependent and most free. Also share my progress.

I can also report the problem, because until recently I was aware of its consequences, but not its origin.
Being aware of the root problem is the only way to find true solutions, and not patches.
We have a problem, and it is UNIX mode.