With automatic repositories, distributing the packages in different directories can quickly become an untamable beast, it also spends a lot of space and bandwidth, and there are too many packages (like the documentation, for example) which are the same for all architectures.
In these cases, one possible solution is a pond. An additional pond is a directory within the repository's root directory, which contains all the packages (the binaries for all architectures, distributions and components and all sources).
You can avoid many problems, through an intelligent combination of prevailing files (item that is not touched in this document) and scripts. A good example of a reposotorio "stagnant" is the repository of Debian.
The ponds are only useful for large repository. I've never done one and I do not think so in the near future and that is why is not explained how to do it here. If you think that this section should be added feel free to contact me and then write one.
Tools
There are several tools to automate and facilitate the creation of files Debian. Below are listed the most important:
apt-ftparchive: The command line tool used to [b] create [/ b] index files that APT uses to access the source of a distribution.
apt-move: It is used to move a collection of files Debian packages to a file hierarchy as used in the file official Debian. This is part of the package apt-utils.
Popularity: 1% [?]
