[maemo-developers] extras vs. extras-devel: how to handle new bindings and developer packages in Fremantle?

From: Andrew Flegg andrew at bleb.org
Date: Sat Nov 7 16:22:43 EET 2009
2009/11/7 Benoît HERVIER <khertan at khertan.net>:
> 2009/11/6 Andrew Flegg <andrew at bleb.org>:
>> I see no need to promote developer dependencies separately, as any app
>> relying on them will have to go through -devel anyway.
> So it s mean that people who want doing some python script on their
> maemo device need to activate before extras-devel repository ? I'm not
> sure this is the best idea ...

I'm not following what you're arguing for. Python is in Extras, -devel
and -testing. Are you saying that random Python bindings - unused for
any particular application (and therefore untested and untestable)
should be promoted on their own; to allow advanced users to install
them and develop Python apps on their tablets?

Developers can enable -devel and use apt-get. Ideally, they'd turn it
off again afterwards. What's the problem?

> But currently the people testing complain about promoting things into
> extras which are not gui things ....

People have complained about non-GUI apps in "user/".

> And adding repository mean asking to user which want to use this yet
> unused binding to add an other repository ? we will be back to the
> repository mess we know some years ago.

 * Most people will have 1 repository (Extras).
 * People willing to test and help with community QA will have 2 (although
   it might as well be one): Extras-testing and Extras.
 * People /developing/ applications on their tablets directly can have
   3: Extras-devel, Extras-testing and Extras.

Also, each repository is a subset of the other; how is this similar to
the repositiory mess?



Andrew Flegg -- mailto:andrew at bleb.org  |  http://www.bleb.org/
More information about the maemo-developers mailing list