I notice on an old thread that work had been done into planning how to merge separate package's .db files into the central .db file.
What was decided? A post install script that scans for .db files and merges them? How are they unmerged when the package is removed?
On Tue, 2005-06-14 at 22:07 -0500, Jerry Haltom wrote:
I notice on an old thread that work had been done into planning how to merge separate package's .db files into the central .db file.
What was decided? A post install script that scans for .db files and merges them? How are they unmerged when the package is removed?
The central .db file is /usr/lib/gcj-4.0.0/classmap.db
jar specific .db files go in the directory /usr/lib/gcj-4.0.0/classmap.db.d. See below for the contents of my FC4 system's directory.
RPM post install and uninstall scripts build the classmap.db file from scratch using /usr/bin/rebuild-gcj-db, which is part of the java-1.4.2-gcj-compat package. So there's no real "unmerging" happening - just rebuilding from scratch. It's a very fast process.
$ ls -l /usr/lib/gcj-4.0.0/classmap.db.d/ total 63560 -rw-r--r-- 1 root root 3522560 May 23 06:30 ant-1.6.2.db -rw-r--r-- 1 root root 352256 May 19 08:41 eclipse-bugzilla.db -rw-r--r-- 1 root root 430080 May 23 12:26 eclipse-cdt.db -rw-r--r-- 1 root root 352256 Apr 26 21:26 eclipse-changelog.db -rw-r--r-- 1 root root 3522560 May 22 12:14 eclipse-ecj.db -rw-r--r-- 1 root root 3522560 May 22 12:15 eclipse-jdt.db -rw-r--r-- 1 root root 3522560 May 22 12:15 eclipse-pde.db -rw-r--r-- 1 root root 3522560 May 22 12:17 eclipse-platform.db -rw-r--r-- 1 root root 352256 Apr 26 16:11 eclipse-pydev.db -rw-r--r-- 1 root root 3522560 May 23 06:49 jakarta-commons-beanutils-1.7.0.db -rw-r--r-- 1 root root 3522560 May 23 06:55 jakarta-commons-collections-3.1.db -rw-r--r-- 1 root root 3522560 May 23 07:14 jakarta-commons-digester-1.6.db -rw-r--r-- 1 root root 3522560 May 23 07:48 jakarta-commons-el-1.0.db -rw-r--r-- 1 root root 3522560 May 23 07:56 jakarta-commons-logging-1.0.4.db -rw-r--r-- 1 root root 3522560 May 23 08:47 jakarta-commons-modeler-1.1.db -rw-r--r-- 1 root root 8192 Apr 22 11:42 jsch.db -rw-r--r-- 1 root root 3522560 May 22 12:17 libswt3-gtk2.db -rw-r--r-- 1 root root 3522560 May 6 06:29 mx4j-2.1.0.db -rw-r--r-- 1 root root 3522560 May 5 06:21 regexp-1.3.db -rw-r--r-- 1 root root 3522560 May 10 03:40 struts-1.1.db -rw-r--r-- 1 root root 3522560 May 10 03:58 tomcat5-servlet-2.4-api-5.0.30.db -rw-r--r-- 1 root root 3522560 May 5 06:19 xerces-j2-2.6.2.db -rw-r--r-- 1 root root 3522560 May 5 06:26 xml-commons-1.0.db
Okay I noticed them. Hadn't seem them.
dbLocation=`/usr/bin/gcj-dbtool-4.0 -p $1` dirname $dbLocation | xargs mkdir -p (cd $dbLocation.d; ls . | xargs /usr/bin/gcj-dbtool-4.0 \ -m $dbLocation)
This seems to assume that the dynamically generated .db is in the same location as the package .dbs... Sort of a FHS violation. We (debian/ubuntu) will be sticking the dynamic db in /var and the package ones in /usr someplace.
I can mod this script to accept a source and destination argument. Is this suitable with you all?
On Wed, 2005-06-15 at 09:13 -0600, Tom Tromey wrote:
"Jerry" == Jerry Haltom wasabi@larvalstage.net writes:
Jerry> What was decided? A post install script that scans for .db files and Jerry> merges them?
BTW the support scripts are all in the 'java-gcj-compat' module of rhug.
Tom
-- fedora-devel-java-list mailing list fedora-devel-java-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
Jerry Haltom wrote:
This seems to assume that the dynamically generated .db is in the same location as the package .dbs... Sort of a FHS violation. We (debian/ubuntu) will be sticking the dynamic db in /var and the package ones in /usr someplace.
That does sound better, from a FHS point of view.
I can mod this script to accept a source and destination argument. Is this suitable with you all?
It'd be nice if it did the new thing with the same old arguments, so I don't have to modify all my rpms ;)
Gary
java-devel@lists.fedoraproject.org