freight-cache
- (re)builds package repositories
freight cache
[-k
] [-g
email] [-p
passphrase file] [-c
conf] [-v
] [-h
] [manager/distro][...]
freight-cache
converts each manager/distro given into a package repository (only Debian archives are supported currently). The manager indicates the type of repository (again, apt
is the only supported value). The distro is an arbitrary string that should match a release of the target operating system (for example, "lenny" or "lucid"). If none are given, freight-cache
converts all manager/distro pairs found in $VARLIB
.
Packages are read from the Freight library ($VARLIB
in the configuration, see freight
(5)) and organized into a working repository in the Freight cache ($VARCACHE
in the configuration).
Serving the repositories is left as an exercise for the reader. The Freight cache is the only directory that needs to be exposed, so create a virtual host with $VARCACHE
as its document root and everything will be fine.
From version 0.0.8 onwards, distros in an APT repository no longer share the contents of the pool/
. After upgrading to this version and running freight-cache
for all your distros, it is safe and recommended to rm -rf $VARCACHE/pool/main
to reset link counts to the proper value.
-k
, --keep
-g
email, --gpg=
email-p
passphrase file, --passphrase-file=
passphrase file-a
digest algorithm, --digest-algo=
digest algorithm-c
conf, --conf=
conf-v
, --verbose
-h
, --help
freight
(5)./pubkey.gpg
FREIGHT_CONF
freight
(5).The New Pornographers - "All the Old Showstoppers"
Richard Crowley r@rcrowley.org
Part of freight
(1).
freight-add
(1) adds packages to the intermediate "Freight library" that is used by freight-cache
to build the actual repositories.