Le jeudi 09 septembre 2010 à 15:25 +0200, Thiago Macieira a écrit : > Em Quinta-feira 09 Setembro 2010, às 14:37:56, Frederic Crozat escreveu: > > > Therefore, if we say that "a MeeGo-compliant RPM is allowed to declare > > > dependencies to the packages on MeeGo Core", is that a problem for SUSE > > > MeeGo? Declaring dependencies implies that all MeeGo-based distros and > > > devices carry the exact same package names and versions, differing only > > > on build numbers (the release). > > > > Ok for package names. For version, we should have the same version or > > maybe more recent version (I don't think it has happen yet, but it could > > happen, who knows). > > We have to check if upgrading beyond patch-level fixes is acceptable. > > I would prefer that it is, but I can come up also with a couple of arguments > against that.
I can understand why it could be a bad idea ;) As I said, it hasn't happened yet. > > > We're also saying that you can't remove any package from the Core > > > repository. > > > > I've checked and we ship almost everything : I'm not sure about > > cross-gcc stuff, but I might be wrong. > > Hmm... then I think we have stuff in Core that shouldn't be there. In fact, > I'd > propose reserving Core to "what must be available for on-device usage, all > devices". SDK tools must definitely be present too, but in a separate > repository. That would be nice. > > > I'd like to see that the MeeGo Extras/Community repository be allowed > > > too. How would this affect SUSE MeeGo? How is it possible to guarantee > > > that this repository is compatible with any vendor's variant? > > > > For SUSE MeeGo, I think it should work "out of the box", since we ensure to > > use similar OBS setup as the one used on "upstream" MeeGo and our package > > are based on "upstream" MeeGo (if not the same). > > That's good. But I didn't understand if you meant that you'd simply rebuild > all the apps in Extras/Community, or if you'd use the existing one. We haven't discussed this yet. For now, the few packages in Extras have been merged in our SUSE MeeGo repository but I'm not sure we will do so in the future. And For Community, I'm not sure either. It would probably better (but not easier) to use existing (ie upstream) repositories. > > I see one possible issue : > > Core/Netbook repositories might not be enabled by default. Same for > > MeeGo Extras/Community. > > I'd say that the distribution must come with a Core repository enabled and > one > for its vertical, at minimum. That doesn't mean it has to be the same one > from > MeeGo upstream. Yes, it should be specified somewhere. > If SUSE MeeGo rebuilds some or all of the packages, it can point to its own > Core repository. The same would be natural for a build for a different > architecture, like MIPS: there is no upstream meego.com MIPS repository to > point to. Agreed. -- Frederic Crozat <[email protected]> Novell _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
