On 2010-07-09, at 3:23 PM, Felipe Contreras wrote: > 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. > Both suse and fedora have package review and acceptance guidelines, if a package is submitted that does not comply, it is rejected. There is no rule that an upstream spec file has to be accepted as is, it really needs to comply with the distro. Depending on how complex it is, it might be accepted as, but that is no rule.
> But on MeeGo it would be rejected. if it does not comply, then it is rejected, what is the problem with that? > >>> 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]. If a package spec file was generated using spectacle, then it only makes sense to include it in the source rpm. So if someone downloads the source rpm, they will also have the input and if they would need to make changes, they can use spectacle. If your package does not use that, then you do not need to worry about it. We also clarified 1 week ago and on the wiki that it is NOT mandatory for all packages, it is however recommended for packages that are generic enough to be converted. Anas > > [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 _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
