Le mercredi 06 janvier 2010, à 17:23 +0000, Michael Meeks a écrit :
The Moblin:Factory packages break down into several pieces.
* Bits already in openSUSE:Factory A. Bits that are the same + no action required.
Yay, easy :-)
B. Bits that are different + telepathy patches
Patches? Any reason they are not committed upstream?
+ some speed optimisations
Hrm, if the optimizations are not accepted upstream, we can do a big "%if MOBLIN_BUILD" for those patches -- quite easy.
* Bits that are not (yet) C. sharable bits that are not * ccss, librest, nbtk, jana ... whatever ... + some of these may be picked up as GNOME deps in future.
Those ones are easy, and I expect they don't need much patches? I can just take them somewhere. The question is where (see below).
D. non-sharable - moblin specific bits * netbook-manager-netbook * moblin-panel-*
Well, we still want them -- so it's a bit like C, we just need to know where to put them.
* mutter / mutter-moblin + potentially fragile, and depend on mutter version GNOME's mutter version is different - urk. + I guess we need to hack these about
The simple solution would be to have a mutter-moblin package that conflicts with mutter, but that means it won't be possible to get gnome-shell and moblin installed at the same time...
E. base-O/S changes + we have quite a few here - from aaa_base to
(I don't think I can help there?)
Of course, it would be possible to have Moblin:Factory to be the source for openSUSE:Factory for C. and D. - with some fun around the mutter situation (I suppose).
I think Moblin:Factory makes sense if its primary target is Factory. This means people will be able to submit changes, update things, etc. that might break on 11.2 or SLE11. We'll try to avoid that, but it will happen. If Moblin:Factory cannot work this way, I suggest using another project. I don't think it should be GNOME:Factory, but we can use something like GNOME:Moblin, if we want (it will just be highly confusing ;-)). (Note that some packages that were originally in C might have made their way into factory via GNOME:Apps or GNOME:Factory)
Pieces in 'B' could be made as (some sort of?) build conditional patches in G:F (and G:Apps ?) - how would that work obs wise ? is that even a good idea. Please bear in mind that '_link's essentially don't work, so I would strongly prefer a solution that is not based on them. Of course, we want to get some of the performance wins into SP1 too.
(would be interesting to evaluate the new branch mechanism that is available in OBS) [...]
One of the problems with slaving M:F to openSUSE - is that we have a different, more rapid development schedule, and of course we badly need to build against a SLE11 base as well as 11.2 - which may require some accommodation ( is this best achieved with .spec file conditionals ? ).
Needing to build against SLE11 is not a big big issue -- we do that all the time for old versions of openSUSE, and it's more or less like building against 11.1 (+ some new packages).
Anyhow - I'd love some input here and/or unstructured thoughts for synthesis. If we can't come to some conclusion by mail - there might even have to be a (dreaded) phone meeting (you have been warned).
I love phone meetings! I do my best to never talk, so that's cool with me ;-) FWIW, what is really difficult for me, as of today, is that if I want to start pushing some of the bits to Factory during the next free hour I have, I can't because I have no idea what the status of the packages is, and the fact that the current base is old means, to me, that I either choose to fork stuff or I don't even care to do the work because I'm unsure it'll be accepted in M:F (no idea what are the policies there; and this is related to the fact that the target of M:F is not Factory). Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org