|
From: Paul P. <pog...@gm...> - 2005-03-29 19:41:03
|
Hi, I received this complaint from a user: =09http://gna.org/bugs/?func=3Ddetailitem&item_id=3D2090 After running `configure' script without any parameters, documentation files are all installed under `/usr/local', including OMF files that go to `/usr/local/omf' and ScrollKeeper database files that go to `/usr/local/var/scrollkeeper'. While the former is probably OK, the second prevents help browsers from including the installed help files to global system list of manuals. I'm using a standard `omf.make' file taken from GNOME. It has these lines in opening comments: # Note that you must configure your package with --localstatedir=3D/var= /lib # so that the scrollkeeper-update command below will update the databas= e # in the standard scrollkeeper directory. # # If it is impossible to configure with --localstatedir=3D/var/lib, the= n # modify the definition of scrollkeeper_localstate_dir so that # it points to the correct location. Note that you must still use=20 # $(localstatedir) in this or when people build RPMs it will update # the real database on their system instead of the one under RPM_BUILD_= ROOT. and then: scrollkeeper_localstate_dir =3D $(localstatedir)/scrollkeeper So my questions are: * Is it normal that ScrollKeeper database files go to `/usr/local/var' and not `/var' by default? * How do I ``configure your package with --localstatedir=3D/var/lib''? I= s it assumed that users should run it like =09./configure --localstatedir=3D/var/lib or should I add some magic to the `configure.ac' file? The former seem= s unlikely as most users won't read READMEs unless something really goes wrong... Thank you. Paul |