FS#825 - ghex bug

Attached to Project: Arch Linux
Opened by Jan de Groot (JGC) - Friday, 23 April 2004, 08:41 GMT
Last edited by Dale Blount (dale) - Friday, 23 April 2004, 11:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

The ghex package updated several minuts ago has some bugs:
- schema file doesn't get merged with postinstall script
- no build dependency on intltool

I don't know if it gets automerged when using the --with-gconf thing, but the usual way to get .schema files merged is using gconftool-2 in a postinstall script.

I have a .install script that works at ftp://schoolbak.dyndns.org/gnome25/src/ghex/ghex.install

Most gnome packages nowadays _REQUIRE_ gconf schemas get merged to function, some packages work without that, but expect missing features when not doing so.
This task depends upon

Closed by  Tobias Kieslich (tobias)
Monday, 26 April 2004, 22:32 GMT
Reason for closing:  Fixed
Comment by Tobias Kieslich (tobias) - Friday, 23 April 2004, 12:06 GMT
I thought it could be done easier, so I called gconftool in make install with the passed parameters. This creates the entries and copies them with pacman.(Look at pkg/opt/gnome/etc/gconf/... for the results, They have been identical with what happend with an install script) At least I didn't saw a difference. If you find one let me know, please.
For the install script, I need to castrate the Makefile first since ghex doesn't take care of "--disable-schemas-install". grmpf
For the intltool, yupp, i'll do tomorrow.
Comment by Jan de Groot (JGC) - Friday, 23 April 2004, 19:40 GMT
The problem is, your gconf database is not in $startdir/pkg/etc/gconf/
When you create the package on your system, it changes the gconf keys in the gconf database on your system this way. It also copies the $prefix/etc/gconf/schemas/ghex2.schemas, but copying that file is not enough, gconf needs to know about the file, it needs to get applied to the system gconf database (the file you're referring to in the PKGBUILD, the xml file).
When using the .install script, the gconf schemas get copied to the etc/gconf/schemas directory and those are applied to the system gconf database using gconftool-2 --make-install-rule.
Comment by Ash (Thikasabrik) - Monday, 26 April 2004, 16:12 GMT
ghex package 2.5.2-1 seems to completely ruin the gconf database sometimes - possibly when a version of gconf was previously installed. See http://bbs.archlinux.org/viewtopic.php?t=4144 for some more info.
Comment by Ash (Thikasabrik) - Monday, 26 April 2004, 16:24 GMT
I mean 'when a version of ghex was previously installed'. Oops. Anyway, that was pure speculation.
Comment by Tobias Kieslich (tobias) - Monday, 26 April 2004, 22:32 GMT
Ok. The Makefile is castrated to disable schema install and the gconftool call has moved to an install file. I hope thus trouble is over.

Loading...