Differences between revisions 6 and 7
Revision 6 as of 2005-08-10 15:47:46
Size: 4287
Editor: anonymous
Comment:
Revision 7 as of 2005-10-12 12:39:29
Size: 5652
Comment: Fixed url-syntax. Updated debarchiver/reprepro infos. Added parser script notes.
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
dpkg-scanpackages. Such a topic is also covered by [Oohara Yuuma how-to
http://www.interq.or.jp/libra/oohara/apt-gettable/apt-gettable/
]
and [apt how-to
http://www.debian.org/doc/manuals/apt-howto/ch-basico.html#s-dpkg-scanpackages].
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].
Line 16: Line 14:
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.
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.
Line 23: Line 19:
[[Anchor(repository_dak)]]
Line 35: Line 32:
[[Anchor(repository_debpool)]]
Line 47: Line 45:
[[Anchor(repository_reprepro)]]
Line 51: Line 50:
 * Package: [http://alioth.debian.org/project/showfiles.php?group_id=30039 Packages in Alioth repositories]
 * Distributions: Not yet.
 * Package: http://packages.qa.debian.org/r/reprepro.html
 * Distributions: Sarge (0.3), Sid (0.6)
Line 59: Line 58:
[[Anchor(repository_debarchiver)]]
Line 61: Line 61:
 * Pro:
 * Cons:
 * Package:
 * Distributions: Woody (0.0.18), Sarge (0.1.5), Sid
 * Pro: Easy to use incoming mechanism - even on remote systems - by using a cron-job. Packages can be moved into a distribution by a) reading the Distribution value from .changes file or b) directly putting the whole package into a distributions-incoming directory.
 * Cons: No Pool-architecture at the moment. Some useful checks are missing. Cleaning needs to be done manually.
 * Package: http://packages.qa.debian.org/d/debarchiver.html
 * Distributions: Woody (0.0.18), Sarge (0.1.5), Sid (0.5.x)
Line 68: Line 68:
 * Pools: No
 * GPG signing:
 * Pools: No (but suggested somewhere at [http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=debarchiver BTS]).
 * GPG signing: Yes (with gnupg, post-Sarge feature).
Line 73: Line 73:
[[Anchor(repository_min-dinstall)]]
Line 85: Line 86:
[[Anchor(repository_apt-utils)]]
Line 97: Line 99:
[[Anchor(repository_dpkg-dev)]]
Line 114: Line 117:
 * [http://elonen.iki.fi/code/parse-apt-files.inc parse-apt-files.inc] PHP-script by Jarno Elonen produces a nice [http://elonen.iki.fi/code/unofficial-debs/ XHTML-summary] of available packages in a repository - [http://debian.wgdd.de/debian/parse-apt-files.inc enhanced version] for special usage with (but not limited to) [#repository_debarchiver debarchiver]. There seems to be some [http://potatosalad.gotdns.com/2005/08/01/repository/ efforts] to develop a wordpress-plugin based on these scripts.

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