[maemo-developers] extras vs. extras-devel: how to handle new bindings and developer packages in Fremantle?
From: Andrew Flegg andrew at bleb.orgDate: Fri Nov 6 19:28:12 EET 2009
- Previous message: extras vs. extras-devel: how to handle new bindings and developer packages in Fremantle?
- Next message: extras vs. extras-devel: how to handle new bindings and developer packages in Fremantle?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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/
- Previous message: extras vs. extras-devel: how to handle new bindings and developer packages in Fremantle?
- Next message: extras vs. extras-devel: how to handle new bindings and developer packages in Fremantle?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]