genbasedir - generates APT RPM repository control files

genbaselist [OPTION...] TOPDIR [COMPONENT...]

genbasedir analyzes the RPM packages in a directory tree and builds information files so that that directory tree can be used as an APT repository. See the examples and references below for how to do that in detail.

-s, --sign

Generate and sign hashfile

--default-key=ID

Use ID as gnupg secret key

--hashonly

Do hash stuff only

--listonly

Generate pkglists/srclists and quit

--partial

Update just some of the already existent components

--oldhashfile

Enable generation of old hashfile

--bz2only

Generate only compressed lists

--progress

Show progress bars for genpkglist/gensrclist

--updateinfo=file

Update information file

--flat

Use flat repository, where SRPMS and RPMS are in TOPDIR (SRPMS are usually in TOPDIR/..)

--bloat

Do not strip the package file list, needed for some distributions that use non-automatically generated file dependencies

--meta=name

Create a meta repository named name

--compresslevel=n

Set bzip2 compress level (0-9)

--cachedir=dir

Use a custom md5sum cache directory for package list generation (useful for non-root users)

--help, -h

Display help

[niemeyer@ibook /pub]% find /pub
/pub 
/pub/conectiva 
/pub/conectiva/RPMS.general 
/pub/conectiva/RPMS.general/dummy-1.0-1cl.noarch.rpm 
 
[niemeyer@ibook /pub]% genbasedir /pub/conectiva 
Creating base directory... done 
Components: general 
Processing pkglists... general [done] 
Processing srclists... [done] 
Creating component releases... general [done] 
Creating global release file... [done] 
Appending MD5Sum... general [done] 
 
[niemeyer@ibook /pub]% find /pub                 
/pub 
/pub/conectiva 
/pub/conectiva/base 
/pub/conectiva/base/pkglist.general 
/pub/conectiva/base/pkglist.general.bz2 
/pub/conectiva/base/release.general 
/pub/conectiva/base/release 
/pub/conectiva/RPMS.general 
/pub/conectiva/RPMS.general/dummy-1.0-1cl.noarch.rpm 

Here is a hint how the directory names, component names, URLs, and sources.list entries fit together: Say the sources.list line is:

rpm http://hostname/dir1 dir2/dir3 component

This would require that the files http://hostname/dir1/dir2/dir3/base/release.component and http://hostname/dir1/dir2/dir3/base/pkglist.component.bz2 be accessible through the web server.

genpkgdir(1), gensrclist(1), https://moin.conectiva.com.br/AptRpm/Repositories

This manual page was written by Peter Eisentraut for the Debian project.