- 31 Oct, 2016 1 commit
-
-
Gleb Fotengauer-Malinovskiy authored
Old format: rpm [p7] http://ftp.altlinux.org/pub/distributions/ALTLinux/p7/branch x86_64 classic New format: rpm [p8] http://ftp.altlinux.org/pub/distributions/ALTLinux p8/branch/x86_64 classic
-
- 24 Mar, 2014 1 commit
-
-
Michael Shigorin authored
Installation finishes just fine if bzip2-compressed hash files are removed *but* apt-cdrom add will fail.
-
- 17 Mar, 2014 1 commit
-
-
Gleb Fotengauer-Malinovskiy authored
This is about (a)synchronous package builder in fact.
-
- 03 Sep, 2012 1 commit
-
-
Michael Shigorin authored
See http://www.opennet.ru/openforum/vsluhforumID3/86239.html#1 for a query that has led to this one; in particular, - xdm dropped (won't log in root and there are no users yet); - network is brought up and configured via DHCP by default; - apt-get works out-of-box; - default image size is twice the chroot size.
-
- 10 May, 2012 1 commit
-
-
Michael Shigorin authored
This further refines the modular build by making metadata being a clearly separated feature rather than having to rely on runtime tests, and also by moving the code which cares for kernel bits of base installation (.base list) in a feature of its own. There's more to it but let's get the ball rolling first.
-
- 02 Dec, 2011 1 commit
-
-
Michael Shigorin authored
Just a hook to export alt-gpgkeys pubring data.
-
- 19 Nov, 2011 2 commits
-
-
Michael Shigorin authored
The features might get copy-pasted (or even copied-and-pruned) when initialized; there's an unneccessary duplication of the function name in the line adding it to FEATURES list, thus prone to being forgotten and causing some havoc later on. It was wrong in the first place but tackling this with some double-colon rules ran into terminality issues, and further tortures were considered unneccessary. The current solution isn't perfect (no completely transparent function name registration upon corresponding target being called) but at least it is an improvement...
-
Michael Shigorin authored
We've got some parts of it in build-distro feature, and some went to dev feature for no real reason. But a bare installer might go without package base, and LiveCDs other than live-builder might find local repository useful given aufs2 root overlay. Now the overall scheme is more straightforward: - a distro: + asks that a package repo be included + cares to further add the packages to it - a repo feature: + pulls in sub/main for it to happen + provides genbasedir script to create repo metadata + supplements live feature with repo configuration
-