On Tue, Jun 14, 2011 at 1:52 AM, Dominig ar Foll <[email protected]> wrote: > those who have discussed with me during the MeeGo Conference in San > Francisco, know that I have started a small project to create a Light > version of OBS. > > The goal of the project is to ease the access to OBS for embedded > developers and initial investigation team which have to select an > embedded OS, by creating a tool which follows their traditional > development process (working locally in chroot) but keeps the > compatibility with the OBS. > > Some of the module that we are planning could potentially be of interest > for the real OBS (called Full OBS in my spec). In particular the the > automatic creation of patch files from a modified chroot and the UI for > MIC2 could become generic features. All created new code will be GPL2. > > Your feedback is welcome. All discussion will take place on the MeeGo > distribution-tools mailing list.
Dominig, it's a bit unclear why this is needed: - Why is current OBS insufficient for your development model? Would running another instance of OBS not suffice? - Why can't the current OBS software be enhanced to better provide the needed features? I'm sure nobody will object against you undertaking this effort, but, if we can extend the current OBS to provide the features needed, we should be in a much better shape going forward: I can only imagine how horrible it will be to maintain a secondary toolset based on a non-stable OBS API if upstream is unwilling to cooperate. Auke _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
