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@xxxxxxxxxxxxxxx> 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@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-devel-java-list -- Jerry Haltom <wasabi@xxxxxxxxxxxxxxx>
