elementary-dev-community team mailing list archive

[Pim Vullers <pim@xxxxxxxxxxxxxx>]

I guess that only is the GSettings issue again. But becomes hard with
things like euclide which is build on top of scratch. Actually it is
scratch with a specific set of plugins, which in this case would need to
be loaded from a different location instead of a central directory. That
would cause the troubles. Actually anything with plugins I guess.

On 06/14/12 21:19, Cassidy James wrote:
> What about something like, say, Scratch? Is it just a minor tweak in the
> packaging, or is it a bigger change in the actual code?
> 
> On Thu, Jun 14, 2012 at 10:45 PM, Pim Vullers <pim@xxxxxxxxxxxxxx
> <mailto:pim@xxxxxxxxxxxxxx>> wrote:
> 
>     On 06/14/12 19:46, Cassidy James wrote:
>     > Hey everyone,
>     >
>     > I've been checking into the requirements for uploading apps to
>     USC, and
>     > I came across an interesting bit here:
>     >
>     >     In order for your application to be distributed in the Software
>     >     Centre it must:
>     >
>     >       * Be in one, self-contained directory when installed
>     >
>     >       * Be able to be installed into the /opt/<package-name>
>     directory (*)
>     >
>     >       * Be executable by all users from
>     >         the /opt/<package-name> directory (**)
>     >
>     >       * Write all configuration settings
>     >         to ~/.config/<package-name> (This can be one file or a
>     directory
>     >         containing multiple configuration files)
>     >
>     >
>     >     (*) Open source, zero-cost apps should be installable
>     >     to /opt/extras.ubuntu.com/ <http://extras.ubuntu.com/>
>     <http://extras.ubuntu.com/><package-name>
>     >     (**) Users only have read and not write privileges to this
>     directory
>     >
>     >
>     > Would our apps fit these requirements? If not, how much work would
>     it be
>     > to make them fit the requirements?
> 
>     For files this is not much of a problem. This can be achieved by setting
>     the install prefix to /opt/<package-name>/. The issue is GSettings
>     (these schemes are currently installed in /usr/share/glib-2.0/schemas).
> 
>     I don't know if Granite will also be offered through this way. But
>     libraries might also cause issues. This approach would require apps to
>     bundle custom libraries, or there must be some mechanism to add
>     /opt/<library-name/lib or so to the library path.
> 
>     So the major issue is the GSettings schemes. Otherwise I see no issues
>     for small apps. For larger apps it will be harder to achieve.
> 
>     Pim Vullers
> 
> 
> 
>     --
>     Mailing list: https://launchpad.net/~elementary-dev-community
>     Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
>     <mailto:elementary-dev-community@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~elementary-dev-community
>     More help   : https://help.launchpad.net/ListHelp
> 
>