packages/dbscripts.git - Arch dbscripts ported to Parabola

Age	Commit message (Collapse)	Author
2018-10-03	config: Add more repos to default ARCHTAGS for db-import-pkg	Luke Shumaker
	This adds staging and testing repos, which we mostly don't currently import. The only bits of this change that I don't feel 100% about are the Arch Linux ARM repos. <https://labs.parabola.nu/issues/1178> packages: + staging-x86_64 + gnome-unstable-x86_64 + kde-unstable-x86_64 community: + community-staging-x86_64 + community-testing-x86_64 + multilib-staging-x86_64 archlinux32: (still leaves out -i486 and releng-x86_64) + community-staging-i686 + community-testing-i686 + staging-i686 + gnome-unstable-i686 + kde-unstable-i686 archlinuxarm: (still leaves out -aarch64, -arm, and -armv6h) + alarm-armv7h + aur-armv7h This also adds a `config-list-tags` script that (like the other `config-*` scripts) helps with writing the config files; it displays discrepancies between the configured ARCHTAGS for an upstream and the list of .db's that fetch_dbs() finds.
2018-09-02	db-import-pkg: Use {PKG,SRC}POOL rather than OUR{PKG,SRC}POOL	Luke Shumaker
	These values should all be the same.
2018-09-02	db-import-pkg: Merge the config in to the main DBSCRIPTS_CONFIG system	Luke Shumaker
	I know, I'm a hypocrite for violating # Please try to refrain from adding new variables to this file. # Instead, create separate ${toolname}.conf files. Only add a # variable here if multiple tools start needing the option. When db-import-pkg moves to use db-{move,update,remove} internally, it will also need to load an upstream-specific config.local.${UPSTREAM} file (the systemd service already sets Environment=DBSCRIPTS_CONFIG=… appropriately, in anticipation of this. This means that the upstream must be specified twice when invoking db-import-pkg; once in the environment, and once in an arg. Right now it (essentially) disregards the environment setting, but that won't always be true. To put a point on that, the test suite currently doesn't set the environment differently for each upstream; once it actually uses the environment, the test suite will "break". So, I'd like to unify these, so that the upstream only needs to be specified once. If we do this as an argument, it will have to get very kludgey with overriding DBSCRIPTS_CONFIG internally, so don't do that. That leaves setting the upstream via DBSCRIPTS_CONFIG= as the only sane option. At that point, it becomes silly to have a tertiary config file (db-import-${UPSTREAM}.conf) that is referred to by the secondary config file (config.local.${UPSTREAM}).
2018-08-23	config.local.{archlinux32,archlinuxarm,community,packages}: set ARCHES	Luke Shumaker

2018-04-29	Use config.local files	Luke Shumaker