On 21.11.2013, at 14:06, Reto Zingg <reto.zi...@jolla.com> wrote: > On 21.11.2013 14:53, Putze Sven wrote: >>> >>> - Shared libraries >>> · You can ship your own private copies of shared libraries that you >>> link against in /usr/share/<name of your app>/, you are not allowed to >>> install shared libraries anywhere else. >> >> Hi, >> >> do I get it right that for each and every App there will be a directory in >> the form >> >> /usr/share/<mydomain>.<mygreatcompany>.<nameofmyapp> > > the folder just exists if the rpm creates it. > >> which is "private" and for App access only? IMHO you could/should create a >> directory standard which should be followed inside this folder. E.g. like >> the bundle folders in the Apple universe. >> > > No, the folder is not private and any app can access it's content. > And no, do not write into the folder at runtime. > > With 'your own private copies of ...' we mean: > your version of a shared library, which we don't want to have installed any > where else in the system (which it might interfere with other apps) and shall > just be used by this very one app.
Sorry, my wording was not precise enough. I meant private in a way that this folder can contain anything that an app needs to run and I want to deliver upon installation. Like, e.g. libraries, images, all kind of resource files, maybe even database templates. I didn't understand it as a runtime work path. I am just picking on this because some mails in this list weren't clear or contradictory. Best. Sven _______________________________________________ SailfishOS.org Devel mailing list
