On 10/20/2010 12:21 AM, Wichmann, Mats D wrote:
There's a fresh draft up, finally:
http://wiki.meego.com/Quality/Compliance#Specification
Please comment on this one.
Line 14: Is this Meego Profile description available in some way
in the system?, for example, in a /etc/profile file or directory,
containing all the metadata (if needed) to identify that system
as of a specific profile, and that could probably be used for
debugging or bug reporting later.
Line 125: Some distributions use some kind of '-rN' suffix to identify
the patched version of the package, should we probably use something
like that here?
Line 188: Though I understand the idea is to have "updated/latest"
packages when possible, what if we instead offer a set of .config
options that a specific linux kernel must follow to be Meego compliant.
(This could also implicitly imply a minimum kernel version).
Note: last time, the issue of dependencies,
or not, generated a lot of heat. This version
states pretty clearly that dependencies outside
the required minimum install are not allowed.
That's simply the current direction, I can't
predict if a future direction will expand the scope.
This version contains a package list, but no version
numbers.
-- mats
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
