On Wed, Feb 05, 2003, [EMAIL PROTECTED] wrote: > Do you have any examples on using ``openpkg index''?, and perhaps > some sample configuration files?
Nothing to configure with "openpkg index". It either reads a source directory containing .spec-files (i.e. our CVS tree) or it reads a directory that contains RPMs and then builds the index, which is basically a more formal format to represent the package data. When it indexes source RPMs it simply extracts the .spec-files. When it indexes binary RPMs it puts the output of rpm -qi into the index. Note that it cannot read or understand arbitrary .spec-files, it uses a simple parser that only understands the openpkg .spec-files that have to follow some tight conventions. openpkg index -o 00INDEX.rdf <dir> -> indexes spec-files openpkg index -o 00INDEX.rdf -i <dir> -> indexes RPMs You can use "-C cache.db" with the latter to cache extracted .spec-files in a database. You need to have the perl module DB_File (package perl-db) installed. With "-c" the output is piped through bzip2 (use -o 00INDEX.rdf.bz2 or similar). The -r is used to denote the RDF "resource" that is referenced in upper-level indexes. If you index binary RPMs you must specify "-p platform" and all RPMs must be for the specified platform. openpkg build uses the same string to identify RPMs that it can install. The string itself is arbitrary but best is to follow some convention, e.g. ix86-freebsd4.7 or x86-debian2.2. Have a look at ftp://ftp.openpkg.org/release/1.2/BIN/00INDEX.rdf Greetings, -- Michael van Elst [EMAIL PROTECTED] ______________________________________________________________________ The OpenPKG Project www.openpkg.org Bug Database Interface www.openpkg.org/bugdb Bug Database List [EMAIL PROTECTED]
