On Fri, Jul 9, 2010 at 8:53 PM, Greg KH <[email protected]> wrote: > On Fri, Jul 09, 2010 at 08:35:39PM +0300, Felipe Contreras wrote: >> So one would expect that such distro-agnostic spec file can be use in >> MeeGo too, right? > > Yup, and it works just fine, I built a number of MeeGo packages just > this week, in the openSUSE obs, and they work wonderfully.
No, I meant the other way around. Suppose git wasn't packaged, the official tarball has a git.spec that is distro-agnostic. If you were to submit it to Fedora for inclusion, it would be accepted, I suppose it would also be accepted on openSUSE. But on MeeGo it would be rejected. >> Wrong. MeeGo doesn't use spec files at all (which is how RPMs are >> supposed to be built). Instead, maintainers are supposed to write >> spectacle YAML files which are used in turn to generate spec files. > > Um, they do? Since when? Did something change since this past > Wednesday when I built these packages? Oh, they build fine, as OBS doesn't need spectacle YAMLs. The issue is about MeeGo _guidelines_, according to Arjan van de Ven, the spectacle YAMLs should also be there[1]. [1] http://lists.meego.com/pipermail/meego-packaging/2010-July/000411.html -- Felipe Contreras _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
