aurweb/support
Dan McGee 7c91c59245 Remove Dummy Package concept
Instead, we just store dependencies directly in the PackageDepends
table. Since we don't use this info anywhere besides the package details
page, there is little value in precalculating what is in the AUR vs.
what is not.

An upgrade path is provided via several SQL statements in the UPGRADING
document. There should be no user-visible change from this, but the DB
schema gets a bit more sane and we no longer have loads of junk packages
in our tables that are never shown to the end user. This should also
help the MySQL query planner in several cases as we no longer have to be
careful to exclude dummy packages on every query.

Signed-off-by: Dan McGee <dan@archlinux.org>
Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
2011-04-03 22:59:32 +02:00
..
schema Remove Dummy Package concept 2011-04-03 22:59:32 +02:00
scripts Remove Dummy Package concept 2011-04-03 22:59:32 +02:00
README.txt initial import 2004-06-13 18:15:49 +00:00

The schema dir contains the AUR database schema file.

The scripts dir will contain any supporting scripts for the AUR such
as the script that handles moving newly uploaded packages via tupkg
to the AUR.