- 31 Aug, 2020 3 commits
-
-
Michael Shigorin authored
Still have to refer to MCST instead at the moment... Fixes: f1c5f98795a698fdd665c7286f15d6e023195200
-
Michael Shigorin authored
SYSLINUX happens where GRUB happens too, just in case. The problem at hand is that some branding-*-bootloader tend to *create* /etc/sysconfig/grub2 without bothering to check that it existed, thus confusing the subsequent scripts (e.g. 65-serial.sh tries to run update-grub that's just absent then).
-
Michael Shigorin authored
Have to refer to MCST instead at the moment.
-
- 17 Jul, 2020 1 commit
-
-
Anton Midyukov authored
See-also: c0c5c94b
-
- 01 May, 2020 1 commit
-
-
Anton Midyukov authored
Partially this is a return of the commit 35db7537. For branding packages, regexp is used. Therefore, it makes no sense to limit them to architectures. use/plymouth and use/syslinux was fenced separately.
-
- 20 Jan, 2020 1 commit
-
-
Anton Midyukov authored
See-also: commit e4bb1727
-
- 19 Aug, 2019 1 commit
-
-
Gleb Fotengauer-Malinovskiy authored
Plymouth is (much more) portable, but our branding packages contain bootsplash designs only on x86 nowdays.
-
- 25 Jul, 2018 1 commit
-
-
Michael Shigorin authored
There's an ISO9660 COPY tag for license info file; make use of it, factoring use/docs/license out while at that. One of the goals was to make it hold the reference to reference to GPL in regular builds and starterkits ;-)
-
- 07 Aug, 2015 1 commit
-
-
Michael Shigorin authored
(rather cosmetic changes)
-
- 10 Mar, 2014 1 commit
-
-
Michael Shigorin authored
Added use/branding/slideshow/once as one of the uses albeit the interface is universal; see this page for more info: http://altlinux.org/branding/slideshow [ru]
-
- 25 Dec, 2013 1 commit
-
-
Michael Shigorin authored
I don't think we're gonna like plymouth over rescue image anytime soon, especially when it hides the moment when shell pops up somewhere under it without startup-rescue caring to remove the splash. So let's put that $(INSTALL2_BRANDING) into proper stage2 flavours only and avoid choking on missing plymouth as well.
-
- 13 Dec, 2013 1 commit
-
-
Michael Shigorin authored
Everything is handled within mki-copy-efiboot currently but it needs an image to process; extracting one from bootloader branding seems less hassle than forcing it into every flavour of branding.
-
- 24 Nov, 2013 1 commit
-
-
Michael Shigorin authored
branding-*-bootloader was handled for stage1 by syslinux feature but somehow got missed regarding the installed system; let's fix.
-
- 10 Jun, 2013 1 commit
-
-
Michael Shigorin authored
These have been proofread somewhat to correspond to the current state of affairs; a missing one was added for fonts feature.
-
- 22 Nov, 2012 1 commit
-
-
Ildar Mulyukov authored
-
- 28 Jul, 2012 1 commit
-
-
Michael Shigorin authored
It wasn't obvious at all what BRANDING variable is for (at least until the source code and existing configurarion has been examined).
-
- 14 Jun, 2012 1 commit
-
-
Michael Shigorin authored
An initial draft of it was done half a year ago but several tricky thingies had kept the code from showing up as it was rather brittle and incomplete. This implementation involves quite a few changes all over the place but finally works good enough for live and installer images. Please pay attention to the versions of these packages: - installer-feature-setup-plymouth (0.3.2-alt1+) - branding-altlinux-sisyphus (20110706-alt2+ if used) - plymouth (0.8.3-alt20.git20110406+) See also: - http://www.altlinux.org/Branding - http://www.altlinux.org/Plymouth
-
- 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.
-
- 07 May, 2012 1 commit
-
-
Michael Shigorin authored
The initial work covered live images but missed an installer bit (thus notes and slideshow were missing in install2) while forgetting to put branding packages into base list (thus kindly making these available for *manual* installation sometime after, ouch).
-
- 06 May, 2012 1 commit
-
-
Michael Shigorin authored
NB: for the feature to work properly the chosen branding package set should have proper Provides: and Conflicts:, specifically it must explicitly conflict with the most lexicographically cool package set around (these days it's sisyphus-server-light).
-
- 04 May, 2012 1 commit
-
-
Michael Shigorin authored
As duly noted by glebfm@, branding issues need more attention by now since only stage1/install2 got some of it so far in this regard. Hence the dedicated feature comes to the rescue (well no, it doesn't actually mess with rescue!).
-