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

[From: Benoît HERVIER]

2009/11/6 Andrew Flegg <andrew at bleb.org>:
> Anderson wrote:
>>
>>
>> On a related issue, It seems unclear to me where to upload things like
>> new Python bindings to be used by developers. So far the "auto
>> promotion of dependencies" approach has worked for *existing* bindings
>> (such as pygtk, python-hildon), but what about the new bindings that
>> have not yet been used by any application (and thus are only in
>> extras-devel)?
>
> Python (and other apps which may have a library) developers should look in extras-devel before porting it themselves?
>
> Arguably, developers should only have -devel in their SDK sources.list as this is what the auto-builder will compile against.
>
> I see no need to promote developer dependencies separately, as any app relying on them will have to go through -devel anyway.
>
> Cheers,
>
> Andrew
>
> --
> Andrew Flegg -- mailto:andrew at bleb.org  |  http://www.bleb.org/
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>

"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 think it should be promoted to extras...
But currently the people testing complain about promoting things into
extras which are not gui things ....

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.

Cheers,

-- 
Benoît HERVIER - http://khertan.net/