Filesystem compatybility layer
Many closed source software are designed to working with only one operating system. Main problem to creating closed source application to Unix is filesystem hierarchy difference.
We can fix that by using package manager. First of all, RPM's should provide variables for some predefined path, like program data(such like levels), program icons, wallpapers, system-wide configuration, program configuration, etc. There's should exist an library to ask for one of them. It is very similar to XDG_DESKTOP_PATH specification, but much wider.
Second off all we should create /application directory(such like proc) and mount there virtual file system containing links to application resources(in hierarchy defined by package). Mount process would been performed on special library initialization, so application should use special library to be independent.
We can also allow to publish some other information into /application, such like named fifo, new run locking system, etc. /application/pid/resources could contains for example files(name fifo) to be shared between application and another.
Filesystem hierarchy differences are too big matter for developers. We can solve this problem with delivering code source to packagers, but that's no solution for closed source programmers. Imagine developer would prepare application for MacOS X and Linux. Without making rubbish(like in Solaris, which supports many of standards) we can't provide better solution than mine( ;-) ). Developer will compile library with our new Virtual File System library(or better: library providing special interface to asking for information about application virtual filesystem).
Actually it works in this way: file system hierarchy should been fully transparent for user and application will only acts with it.
In my opinion, it's impossible. So makes it different: File System Hierarchy are for administrators, not for applications. User will still don't care about it(it haves /home directory).
Set user benefit
You can add different relations here, for example duplicate features, obs projects, urls...
To embedd an image you can simply upload it to paste.opensuse.org and add a relation to its raw url.
Set release notes
Developer would create closed source application, but filesystem hierarchy difference in each system is too big matter for him.
He create his own hiearchy and tell to packagers: do rest of work.
Create OpenSource application, which uses this library. Create a lot of packages without recombiling(one binary file).
Last change: 3 years ago