On Sat, Jul 10, 2010 at 12:18 AM, Thiago Macieira <[email protected]> wrote: > On Friday 9. July 2010 21.45.26 Felipe Contreras wrote: >> 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". > > That file would be most likely be rejected in Mandriva too, for not following > the guidelines.
Can you point out which specific sections of the guidelines are not met by the distro-agnostic spec file? Or are you just guessing? > Compare with the Mandriva equivalent of the same file: > http://svn.mandriva.com/cgi- > bin/viewvc.cgi/packages/cooker/git/current/SPECS/git.spec?revision=538411&view=markup I already argued that the fact the distribution has a different spec, doesn't mean that the upstream spec doesn't comply. > I'm sorry, but I don't know .spec files to be really cross-distro. It's > something you can base on and adapt to your distro. Unfortunately it seems to be the case. But ideally no changes should be required, and if the changes can be minimized, that's good. > At the very *least*, package names differ from distro to disto. Therefore, all > the Requires and BuildRequires rules are distro-specific. No. Nowadays distros find the Requires automatically (at least for binary packages) based on the link dependencies. Also there's now the pkgconfig() capability, so you don't need to mention the specific -dev package that provides certain .pc file in the BuildRequires. -- Felipe Contreras _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
