On Mon, Sep 20, 2010 at 10:21, Riku Voipio <[email protected]> wrote:
>
> Another thing people here seem to ignore: For developers *not* coming from
> linux distribution/packaging background, importing a shared library to their
> application project is infinitely simpler task than packaging the same
> library (correctly!) and distributing it to a extras-style repository.
Not necessarily: build systems may not be compatible, and it's
unlikely a shared library's tarball will expand into the Qt SDK and
build; surely?
That same developer may not be able to do it the "traditional" Linux
way (i.e. a separate reusable package), but someone else may be able
to. Indeed, this gives a way for others to contribute: "I want to
build an app to do Foo, and it'd be easier if I could use this libbar
- can anyone package it for me?". It gives a separation of concerns.
Anyway, as has been pointed out, we're going round in circles (with
more posts to this thread on the principles than to any of the
concrete suggestions).
I propose:
* we have a "mission statement" or something for Compliance. Quim's tried
to produce one, but it instantly falls apart.
* a wiki page is created where we can pull out the key requirements for
_all_ groups:
o compliance testability
o a measure of guarantee that, given the right hardware (including
architecture, UX, RAM, ...), a user will be able to use a
Compliant application
o requirements for vendors building MeeGo devices
o ease of development
o reuse of work done by others [this is the new one]
o secure
o ...?
* we _then_ focus on the techincal, procedural and process aspects
of compliance to come up with a solution.
Currently, we have a solution posted without clear statements on the
first two bullets; meaning that we're all arguing without fully
understanding *all* the requirements that we want Compliance to meet.
Cheers,
Andrew
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
