Differences between revisions 7 and 8
Revision 7 as of 2005-10-12 12:39:29
Size: 5652
Comment: Fixed url-syntax. Updated debarchiver/reprepro infos. Added parser script notes.
Revision 8 as of 2005-10-12 12:51:40
Size: 5642
Comment: Fixed syntax around PostgreSQL (it's not a WikiName (syntax)).
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
 * Cons: Depends on python and !["PostgreSQL"] (even if on an other host).  * Cons: Depends on python and PostgreSQL (even if on an other host).
Line 76: Line 76:
 * Pro: Doesn't require a !["PostgreSQL"] database.  * Pro: Doesn't require a PostgreSQL database.

This documents summarises what I have found about settling a Debian repository.

I have taken care of providing the most correct information at the time of writing but if you find any inaccuracy, please, fix it.

In [http://www.debian.org/doc/manuals/repository-howto/repository-howto.html Aaron Isotton how-to] two kinds of repositories are defined, the trivial repositories (where the user of the repository has to specify an exact path to the packages) and the automatic repositories (that mimic the official Debian repositories where only the base path, distribution and component have to be specified and the apt-get magic occurs). His how-to describes how to setup trivial repositories with dpkg-scansources and dpkg-scanpackages. Such a topic is also covered by [http://www.interq.or.jp/libra/oohara/apt-gettable/apt-gettable/ Oohara Yuuma how-to] and [http://www.debian.org/doc/manuals/apt-howto/ch-basico.html#s-dpkg-scanpackages apt how-to].

The settling of automatic repositories is covered by [http://familiasanchez.net/~sanchezr/?page=debrepository Roberto Sanchez how-to] who gives relevant scripts. Pools are not covered there.

There are also packaged (or not) tools in Debian in order to perform the task.

?Anchor(repository_dak)

dak (Debian Archive Kit)

?Anchor(repository_debpool)

debpool

?Anchor(repository_reprepro)

reprepro (formerly known as mirrorer)

  • Goals: Local Debian package repository storing files in a pool/ directory.
  • Pro: Strict checking of what comes in, no database server needed.
  • Cons:
  • Package: http://packages.qa.debian.org/r/reprepro.html

  • Distributions: Sarge (0.3), Sid (0.6)
  • Dependencies:
  • Automatic repositories: Yes
  • Incoming mechanism: Yes
  • Pools: Yes
  • GPG signing: Yes

?Anchor(repository_debarchiver)

debarchiver

?Anchor(repository_min-dinstall)

mini-dinstall

  • Goals: Miniature version of dak.
  • Pro: Doesn't require a PostgreSQL database.
  • Cons:
  • Package:
  • Distributions: Sarge, Sid
  • Dependencies: apt-utils, python2.3, python-apt.
  • Automatic repositories:
  • Incoming mechanism:
  • Pools:
  • GPG signing:

?Anchor(repository_apt-utils)

apt-ftparchive

  • Goals: Superset of dpkg-scanpackages and dpkg-scansources.
  • Pro: Does not rely on any external programs aside from gzip.
  • Cons:
  • Package:
  • Distributions: Woody, Sarge, Sid
  • Dependencies:
  • Automatic repositories: No
  • Incoming mechanism: No
  • Pools: No
  • GPG signing: No

?Anchor(repository_dpkg-dev)

dpkg-scanpackages and dpkg-scansources

  • Goals:
  • Pro:
  • Cons:
  • Package:
  • Distributions: Woody, Sarge, Sid
  • Dependencies:
  • Automatic repositories: No
  • Incoming mechanism: No
  • Pools: No
  • GPG signing: No