calculate
/
calculate-plymouth
6
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9795c9b561'
${ noResults }
calculate-plymouth/scripts/Makefile.am

31 lines
1.5 KiB
Raw Normal View History Unescape

add my scripts directory to git
17 years ago
noinst_SCRIPTS = new-object.sh
fix up the scripts Makefile to actually install the script
17 years ago
initrdscriptdir = $(libexecdir)/plymouth
[scripts] add plymouth-generate-initrd script One useful way to use plymouth is by installing it into an auxillary initrd image, that overlays the primary one. This allows plymouth and its current theme to get updated indepedently of the kernel and the rest of the initrd stuff. plymouth-generate-initrd creates an initrd named: initrd-plymouth.img in /boot that is suitable for use a second initrd on the initrd line in grub.conf.
15 years ago
initrdscript_SCRIPTS = plymouth-update-initrd plymouth-generate-initrd plymouth-populate-initrd
add my scripts directory to git
17 years ago
Add new plymouth-set-default-plugin script This script updates which plugin graphical.so points to
16 years ago
sbinscriptsdir = $(sbindir)
[splash] Split splashes into plugins and themes Some of the plugins (well, the glow plugin) would be a lot more versatile if they could be reused for multiple splashes with different images. This commit splits boot splashes into two parts, the plugin engine which does all the dirty work, and the theme which says which plugin to use and optionally how the plugin should work (using plugin specific key/value pairs)
15 years ago
sbinscripts_SCRIPTS = plymouth-set-default-theme
Add new plymouth-set-default-plugin script This script updates which plugin graphical.so points to
16 years ago
Don't ship pregenerated initrd scripts in tarball
16 years ago
plymouth-populate-initrd: $(srcdir)/plymouth-populate-initrd.in
Move plymouth client/daemon/libply out of /usr Since we may be calling plymouth before /usr is mounted we need to make sure it's not in /usr. The daemon could technically stay in /usr/libexec, but if we're moving the client, should move the daemon, too, I guess.
16 years ago
sed -e 's,[@]logofile[@],$(logofile),g' \
-e 's,[@]plymouthclientdir[@],$(plymouthclientdir),g' \
-e 's,[@]plymouthdaemondir[@],$(plymouthdaemondir),g' \
allow to change system release filename with configure option
15 years ago
-e 's,[@]RELEASE_FILE[@],$(RELEASE_FILE),g' \
Move plymouth client/daemon/libply out of /usr Since we may be calling plymouth before /usr is mounted we need to make sure it's not in /usr. The daemon could technically stay in /usr/libexec, but if we're moving the client, should move the daemon, too, I guess.
16 years ago
$(srcdir)/plymouth-populate-initrd.in > plymouth-populate-initrd
run initrd update script after install
17 years ago
[splash] Split splashes into plugins and themes Some of the plugins (well, the glow plugin) would be a lot more versatile if they could be reused for multiple splashes with different images. This commit splits boot splashes into two parts, the plugin engine which does all the dirty work, and the theme which says which plugin to use and optionally how the plugin should work (using plugin specific key/value pairs)
15 years ago
plymouth-set-default-theme: $(srcdir)/plymouth-set-default-theme.in
update libdir detection to reflect to plymouth dir Previously, plymouth was installed in /usr/bin and we'd look for it there to figure out if this is a 64-bit or 32-bit install. Now it's in /bin, so we need to look in /bin instead.
16 years ago
sed -e 's,[@]logofile[@],$(logofile),g' \
-e 's,[@]plymouthclientdir[@],$(plymouthclientdir),g' \
-e 's,[@]plymouthdaemondir[@],$(plymouthdaemondir),g' \
[splash] Split splashes into plugins and themes Some of the plugins (well, the glow plugin) would be a lot more versatile if they could be reused for multiple splashes with different images. This commit splits boot splashes into two parts, the plugin engine which does all the dirty work, and the theme which says which plugin to use and optionally how the plugin should work (using plugin specific key/value pairs)
15 years ago
$(srcdir)/plymouth-set-default-theme.in > plymouth-set-default-theme
update libdir detection to reflect to plymouth dir Previously, plymouth was installed in /usr/bin and we'd look for it there to figure out if this is a 64-bit or 32-bit install. Now it's in /bin, so we need to look in /bin instead.
16 years ago
Gut plymouth-update-initrd It's broken and people keep using it, so change it so that it's useful.
16 years ago
EXTRA_DIST= plymouth-update-initrd \
[scripts] add plymouth-generate-initrd script One useful way to use plymouth is by installing it into an auxillary initrd image, that overlays the primary one. This allows plymouth and its current theme to get updated indepedently of the kernel and the rest of the initrd stuff. plymouth-generate-initrd creates an initrd named: initrd-plymouth.img in /boot that is suitable for use a second initrd on the initrd line in grub.conf.
15 years ago
plymouth-generate-initrd \
Don't ship pregenerated initrd scripts in tarball
16 years ago
plymouth-populate-initrd.in \
[splash] Split splashes into plugins and themes Some of the plugins (well, the glow plugin) would be a lot more versatile if they could be reused for multiple splashes with different images. This commit splits boot splashes into two parts, the plugin engine which does all the dirty work, and the theme which says which plugin to use and optionally how the plugin should work (using plugin specific key/value pairs)
15 years ago
plymouth-set-default-theme.in \
Don't ship pregenerated initrd scripts in tarball
16 years ago
$(noinst_SCRIPTS) \
default.cfg
[splash] Split splashes into plugins and themes Some of the plugins (well, the glow plugin) would be a lot more versatile if they could be reused for multiple splashes with different images. This commit splits boot splashes into two parts, the plugin engine which does all the dirty work, and the theme which says which plugin to use and optionally how the plugin should work (using plugin specific key/value pairs)
15 years ago
CLEANFILES = plymouth-populate-initrd plymouth-set-default-theme
MAINTAINERCLEANFILES = Makefile.in plymouth-populate-initrd plymouth-set-default-theme