aurweb - Arch User Repository

Age	Commit message (Collapse)	Author	Files	Lines
2015-06-16	gendummydata.py: Remove CategoryID from dummy data	Marcel Korpel	1	-3/+3
	Signed-off-by: Marcel Korpel <marcel.korpel@gmail.com> Signed-off-by: Lukas Fleischer <lfleischer@archlinux.org>
2015-06-14	Adding PackagerUID to the generated dummy data	Leonidas Spyropoulos	1	-2/+4
	Signed-off-by: Lukas Fleischer <lfleischer@archlinux.org>
2014-12-13	Fixes incorrect SQLs on generating dummy data.	Shinya Yamaoka	1	-3/+3
	The number of columns in the SQLs doesn't match the number of rows, so an error like below occurs: ERROR 1136 (21S01) at line 50929: Column count doesn't match value count at row 1 Signed-off-by: Shinya Yamaoka <contact@mail.libmacro.com> Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
2014-04-26	Store conflicts, provides and replaces in the DB	Lukas Fleischer	1	-11/+16
	Package conflicts, provides and replaces are now stored in the new PackageRelations table. The gendummydata script generates test entries for these relations. Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
2014-04-17	Store {make,check,opt}depends in the database	Lukas Fleischer	1	-3/+6
	In addition to parsing and storing dependencies of packages, store makedepends, checkdepends and optdepends. Every dependency (of any type) is displayed on the package details page. Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
2014-04-05	Store comments on a per-package base basis	Lukas Fleischer	1	-1/+1
	Move comments from the Packages table to PackageBases. Sharing comments makes sense since they almost always refer to a source package. Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
2014-04-05	Add provisional support for package bases	Lukas Fleischer	1	-6/+10
	This adds a PackageBases table to the database schema and moves the following fields from the Packages table to PackageBases: * CategoryID * NumVotes * OutOfDateTS * SubmittedTS * ModifiedTS * SubmitterUID * MaintainerUID It also fixes all database accesses to comply with the new layout. Having a separate PackageBases table is the first step to split package support. By now, we create one PackageBases entry per package (where the package base has the same name as the corresponding package). When adding full support for split packages later, the package base name will be derived from the pkgbase variable and a single package base will be shared amongst all packages built from one source package. Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
2014-02-06	Move support/schema/ to schema/	Lukas Fleischer	1	-0/+302
	There aren't any other subdirectories in support/. Reduce the nesting depth by moving schema/ to the top-level source directory. Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>