Menu
▾
▴
Re: [Gramps-users] .rpm packages for Fedora
|
From: Graeme N. <gni...@tp...> - 2006-12-27 02:29:15
|
Alex Roitman wrote: > Graeme, > > On Tue, 2006-12-26 at 16:50 +1100, Graeme Nichols wrote: > >>I ran the dry run option and the following is the result: >> >>[graeme@barney gramps-2.2.4]$ patch --dry-run -p0 < no_help.patch >>patching file configure.in >>patching file Makefile.am >>Hunk #1 succeeded at 1 with fuzz 2. >>[graeme@barney gramps-2.2.4]$ >> >>I guess that is all good. > > > Yes > > >>Yes, I am using the ./configure command but there is an autogen.sh >>script in the gramps-2.2.4 directory. >> >>Running ./autogen.sh results in the following: >> >>[graeme@barney gramps-2.2.4]$ ./autogen.sh >>which: no gnome-autogen.sh in >>(/home/graeme/adabas/bin:/home/graeme/adabas/pgm:/home/graeme/adabas/bin:/home/graeme/adabas/pgm:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/graeme/bin) >>You need to install gnome-common package. > > > Right, just as I thought :-) > > >>If you can make the tarball for me I would appreciate it. > > > Here you are: > http://gramps-project.org/files/gramps-2.2.4.tar.gz > > With this you should be able to unpack, cd to gramps-2.2.4 > and then: > $ ./configure --prefix=/usr > $ make > $ su > # make install > > Hope this works, > Alex Hello Alex, [graeme@barney download]$ cd gramps-2.2.4 [graeme@barney gramps-2.2.4]$ ./configure --prefix=/usr checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for perl... /usr/local/bin/perl checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool [graeme@barney gramps-2.2.4]$ I installed the XML::Parser module and it all worked fine. Thank you very much indeed. However using the command rpmbuild -tb gramps-2.2.4.tar.gz fails; See the following; checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-redhat-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GDU_MODULE_VERSION_CHECK... Requested 'gnome-doc-utils >= 0.3.2' but version of gnome-doc-utils is 0.2.0 configure: error: Package requirements (gnome-doc-utils >= 0.3.2) were not met: If I may make a suggestion... You say that gramps does not need gnome-doc-utils-0.3.2 to run. That is obviously correct. The problem is that gramps cannot be built because of the gnome-doc-utils dependency. Would it not be possible to have two configure scripts, one for building gramps and one for building the documentation. The configure script to build gramps can do the check for the correct version of gnome-doc-utils and depending on the result of that check the configure script for building the documentation can be called *after* a successful build of gramps or not called as the case may be. Those distributions with the required version of gnome-doc-utils will have the documentation built. Those that do not have the correct version of gnome-doc-utils can be given a message to download the documentation from the gramps site. Also the documentation can always be built independent of the building of gramps if needed for any reason. Those distributions that use the Red Hat Package Manager can create their own binary .rpm package using the following command: rpmbuild -tb gramps-2.2.4.tar.gz if the configure scripts are set up properly. This means that all the developers need to furnish is the tarball. All the users of rpm based distributions can easily create their own .rpm package using rpmbuild, either binary or source. The other thing that puzzles me is "Why include the building of the documentation in the gramps package when someone is obviously going to a lot of trouble to build it and make it available for download on the gramps site?" Seems to me to be a lot of wasted time and effort duplicating things but I'm sure there is a logical reason. The end result is that gramps, which will happily run on older distributions without gnome-doc-utils, can not be built on older distributions if their version of gnome-doc-utils is not the latest. It seems that there is a catch 22 situation here. Thank you for all your help, it is very much appreciated. I am now running GRAMPS-2.2.4-1.NOHELP and it is *very* good. We gramps users are indeed extremely fortunate. -- ---------------------------------------------------------------------- Kind regards, Graeme. ---------------------------------------------------------------------- Download my GnuPG public key from:- http://www.users.tpg.com.au/gnichols/graemenichols.pub ---------------------------------------------------------------------- Beauty is one of the rare things which does not lead to doubt of God. -- Jean Anouilh |