On Wednesday 28 April 2010 22:12:07 David Greaves wrote: > Well, the build systems team inside Nokia has begun writing some docs to > assist internal developers with much the same issues. We're starting to > publish some of them. A first page came out today > http://wiki.meego.com/Packaging/Deb_conversion_example
Thanks. I have been reading some tutorials as well as the Fedora documentation (which is not as complete as I would like). And this page is certainly useful. I have managed to create (and install) my first rpm but I have a few questions which I haven't found answers to yet: 1) Some of my packages are built from SVN (nightly builds). There are no .tar files, just SVN access. On Maemo I use MUD which effectively fetches the files from SVN into a directory of the right name, applies patches and then invokes the right tools to create the packages. What is the usual way to handle this case in the rpm world? I have yet to find any example which does not use a .tar file for the sources. I currently have a .spec file which uses an empty SOURCES directory and the %prep uses svn to fetch the sources directly into the build directory. This creates a valid binary rpm but does not create a source rpm! I would assume that I could use svn to fetch the source into the SOURCES directory before calling rpmbuild and make the %prep do "cp -r" to copy them. Or I could go the whole hog and fetch the sources from svn into a separate directory, tar it up and put the tar file in SOURCES. Is one of these (or something else) the normal way to handle this issue in the rpm world? 2) It seems that some stuff for the .spec file is often stored in source files instead (the %changelog and the %files sections particularly). Are these normally created using patch files (as they won't normally be in the upstream tar file)? In that case, I presume it is not problem that they don't exist until after the %prep stage. 3) What role is spectacle intended to play? Is this a general rpm-world tool or something meego-specific? Is it completely optional, recommended, or required? The README is useful but some more explanation of how it is actually used would be nice. At first sight it is really not clear what advantage this has over maintaining the spec file itself. 4) What will the input to the build system look like (once it is available)? Will it be like the Maemo autobuilder (i.e. submit a source RPM) or will some other control file be required? 5) I have "glib2-devel" and "gtk2-devel" in my BuildRequires: line. But I have seen (in some mail message) a reference to pkgconfig in the BuildRequires line and, when I tried running spec2spectacle it told me it wanted to see things like "gthread-2.0" (and a bunch of others) in place of these. What should I be using in my BuildRequires: line? Any answers to these questions would be useful. And they might be useful info for other Debian packagers on the Deb conversion wiki page. Graham _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
