On 2/3/11 3:57 PM, "Arjan van de Ven" <[email protected]> wrote:
>On 2/3/2011 3:51 PM, David Greaves wrote: >> On 03/02/11 22:04, Arjan van de Ven wrote: >>> On 2/3/2011 1:02 PM, Shane Bryan wrote: >>>> >>>> I can't see how this is of any concern or issue to the Core OBS team, >>>> or why it's package contents policy must be imposed on the community >>>> OBS. >>>> >>> I'm not trying to impose anything >>> >>> I was trying to point out that the very few things that are going to be >>> ejected is really the bottom of the barrel, obsoleted stuff replaced by >>> newer code. >>> There is no plan to eject things that really have a use (like your tftp >>> example). >> >> Agreed, so as tftp isn't in Trunk anyway; however now the community >> OBS is beginning to take shape it may be worth looking at the packages >> that *are* in Trunk (and elsewhere on the core OBS) and asking what >> value they have to MeeGo's 'real' customers. >> >> And by that I mean the vendors who are going to be building product on >> top of MeeGo. >> >> eg, whilst I swear by it: >> http://build.meego.com/package/show?package=org-mode&project=Trunk >> heck, it's not even mobile-org-mode :) And there's no reason it should be mobile-org-mode. We have 5 verticals. Just because it's in Trunk doesn't mean it's for mobile. We don't have mobile-gcc. >> So if there are things like this that are not really 'Core' material >> and yet take build and QA/validation time in the core then it may make >> sense to clearly differentiate them by moving them out. > >the target is not just people making devices, but for sure also >developers developing on and for meego! > >and my personal opinion is that, even though the community OBS is a >great effort, we must be on a path to just do all of that in the "main" >OBS over time. Completely agree with this. Ryan _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
