[MeeGo-dev] Meego spec - for comment

[Gabriel M. Beddingfield]

On Friday, September 03, 2010 05:59:37 pm Wichmann, Mats D 
wrote:
> There's a rough early version available on
> http://wiki.meego.com/Quality/Compliance

Thank you!

> We'd like to ask for feeback on this at various levels,

General:

   This specification seems to be a mash-up of what is
   a MeeGo-complient DEVICE, and what is a MeeGo-compliant
   APPLICATION/package.  If this is the case, it would
   be worthwhile to clearly distinguish these.  Maybe even
   divide them out.

Repackaging:

   "MeeGo Core: a core set of operating system components
   (or 'stack') as provided by the MeeGo project is always
   required, and may not be replaced or repackaged (see
   Definitions)."

   For some devices (or even applications) it may be  
   necessary to replace the kernel, or even some parts
   of ALSA (e.g. firmware packages).  This can easily be
   done without breaking ABI's.  I'm mostly concerned that
   I would be tied down to MeeGo's kernel and that I won't
   be able to tweak my device to take advantage of its
   hardware.

Installation locations:

   "Application shall be installed to /opt/packagename/ and
   /var/opt/packagename/ directories. System wide 
   configuration files shall be stored in 
   /etc/opt/packagename directory. User specific files 
   shall be stored in ~/.config/packagename directory."

   This seems targeted at app-store-like applications.  
   Right?  And I think it's a good idea.

   But, if I supply extra applications/packages with my 
   device... things that are core to my OEM product...
   is it OK to package them according to LSB?  Obviously,
   all the packages in MeeGo Core have been installed using
   LSB.

Operating system standard locations:

   If I'm writing an app that, for instance, lists all
   the applications installed (*.desktop)... where do
   I go to find these?  According to this, I would need
   to `find /opt -name "*.desktop"`, and there's
   no mention of /usr/share/applications or an LSB spec.

   What I'm getting at (to be a little more clear) is
   that when an application NEEDS something from the
   OS, this spec doesn't provide any information about
   where to go.  Right now, reference to LSB is limited
   to application binary format (ELF).[1]  It might be
   good to appeal to more of the LSB Core[2] and even
   LSB Desktop.[3]

-gabriel

[1] Sect. 3.3
[2] http://refspecs.linuxfoundation.org/LSB_4.0.0/LSB-Core-
generic/LSB-Core-generic/book1.html
[3] http://refspecs.linuxfoundation.org/LSB_4.0.0/LSB-
Desktop-generic/LSB-Desktop-generic/book1.html