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 :)
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.
This would also allow the community - and core - to have a small but visible
reference vendor which has to cope with tracking changes in MeeGo Trunk in order
to be ready for a corresponding release as soon as possible.
Shane, tftp sounds like a good candidate for the embryonic 'Surrounds' area; and
IMHO, so does emacs et al.
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
