systemrescue-zfs/mirrorlist-snapshot-i686

#
# Mirrors for archive.archlinux32.org
# Currently just one stable mirror known, see https://bbs.archlinux32.org/viewforum.php?id=10
#
Server = https://archive.archlinux32.org/repos/%SNAPSHOT_DATE%/$arch/$repo
Build image based on defined repo snapshot date The repo snapshot date is determined automatically by a query to the archive mirror. You can also set a different snapshot date with the -s option. Before always the current packages were used. Use defined snapshots instead, because a future commit will switch pacman within the image to use the snapshot too. 2021-12-05 00:10:40 +01:00			`#`
			`# Mirrors for archive.archlinux32.org`
			`# Currently just one stable mirror known, see https://bbs.archlinux32.org/viewforum.php?id=10`
			`#`
Use snapshot archive repo for pacman in SystemRescue by default This prevents huge dependency downloads by pacman when the SystemRescue version gets older by using a snapshot repo from the day the SystemRescue version is released. The classic rolling repos from Arch are also available as option. Activate with the "--config /etc/pacman-rolling.conf" option to pacman. To allow switching on a per-command basis, two different sets of remote package databases are required. But the local package database must be the same for both variants. This is achived by using two different DBPaths in the pacman config files and bind-mounting the local part together. pacman does not accept symlinks for this, so it must be a bind mount. 2021-12-05 02:08:37 +01:00			`Server = https://archive.archlinux32.org/repos/%SNAPSHOT_DATE%/$arch/$repo`
Build image based on defined repo snapshot date The repo snapshot date is determined automatically by a query to the archive mirror. You can also set a different snapshot date with the -s option. Before always the current packages were used. Use defined snapshots instead, because a future commit will switch pacman within the image to use the snapshot too. 2021-12-05 00:10:40 +01:00