On Fri, Jul 9, 2010 at 9:01 PM, Samir Faci (Dev) <[email protected]> wrote: > An RPM built for FC usually doesn't work on RH, nor would I try to > install an RH rpm on SuSe.
I'm not talking about binary compatibility; I'm talking about spec files. > Every distro has deviation in the names they choose for their > packages. The fact that Meego seems to try to improve and make it > easier to > generate packages. I haven't read up on YAML, but I presume there's a > reason beyond introducing a new feature just to be different and > special. Yes, the people that don't care about being distro-agnostic can use whatever fancy features they want. But us who care about that sort of thing should not be forced to use a format that is not standard among distros. > I don't see what the big deal is. You still end up with a spec file. It's not about taking something from MeeGo, and through some magical process being able build an RPM for another distro. It's about having a spec file that works on Fedora, openSUSE, Mandriva, etc. Those are called distro-agnostic, or multi-distro. Here's one example: http://git.kernel.org/?p=git/git.git;a=blob;f=git.spec.in Such spec files *build* fine on MeeGo, but are rejected for integration because they "don't follow the guidelines". > It's not like debian packages for debian are just like the ones for > Ubuntu. Not all of them but some, the ones maintained by people who care about cooperation are *identical*. -- Felipe Contreras _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
