On Monday 08 March 2010 15:13:33 Arjan van de Ven wrote:
> On 3/8/2010 1:31, Mr. Todorov Todor wrote:
> > Hi,
> > does somebody has experience on deployin POCO (C++ libraries
> > http://pocoproject.org/ ) on MeeGo.
> > Or generally what is your oppinion on making this library available on
> > MeeGo? Todor
>
> the "should this library be included" question usually has 3 components
>
> 1) Is something relevant actually going to use it for some useful
> functionality? (without a "yes" to that it usually is an irrelevant
> library)
> 2) Does it overlap with something that we already have?
>     (if there's overlap, extending what is already there may well be the
> better solution) 3) How is the quality/maintenance/etc?
>     (if the code is full of security holes, or the upstream project is
> mostly dead, then it's probably not a good idea)

Good and useful questions.

But I would also like to understand more about what "included" might mean.  If 
MeeGo were an ordinary distribution (like Debian, say) then "included" would 
mean things like: built as part of the distribution, included in the output 
(repository, CD, ...) of the distribution, supported (at least for bug 
reporting, possibly for security patches) by the distribution.  For most 
distributions the key thing controlling inclusion is someone offering to 
provide the packaging and support required.

But for MeeGo, "included" might mean something different.  It might mean, for 
example, guaranteed to be present on any device which claims to use "MeeGo 
Vx".  Is this going to be true for everything "included" in MeeGo?  Or will 
there be something like Debian's "essential" category: packages guaranteed to 
be present?

Even if not guaranteed to be present, "included" might mean "guaranteed to be 
installable".  I.e. a compliant device does not prevent installation of the 
package and has some way to get it installed.

Or, it might just mean, "available from a repository -- if it installs that is 
fine, if not, tough".  This is likely to be the case for 
community-contributed packages, if they are included in the MeeGo 
repositories at all.

Lastly (I think) it might mean "available from a non-MeeGo repository, 
supplied by the community or a commercial partner, tested with MeeGo".  This 
is pretty close, in my view to meaning "not included"!

Graham
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to