plymouth/scripts/Makefile.am

noinst_SCRIPTS = new-object.sh 

initrdscriptdir = $(libexecdir)/plymouth
initrdscript_SCRIPTS = plymouth-update-initrd plymouth-generate-initrd plymouth-populate-initrd

sbinscriptsdir = $(sbindir)
sbinscripts_SCRIPTS = plymouth-set-default-theme

EXTRA_DIST= plymouth-update-initrd                                             \
	    plymouth-generate-initrd.in                                        \
	    plymouth-populate-initrd.in                                        \
	    plymouth-set-default-theme.in                                     \
	    $(noinst_SCRIPTS)                                                  \
	    default.cfg
add my scripts directory to git 2007-06-08 12:13:45 -04:00			`noinst_SCRIPTS = new-object.sh`

fix up the scripts Makefile to actually install the script 2007-06-08 14:45:30 -04:00			`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. 2009-08-28 20:00:08 -04:00			`initrdscript_SCRIPTS = plymouth-update-initrd plymouth-generate-initrd plymouth-populate-initrd`
add my scripts directory to git 2007-06-08 12:13:45 -04:00
Add new plymouth-set-default-plugin script This script updates which plugin graphical.so points to 2008-06-11 10:21:18 -04:00			`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) 2009-04-29 14:25:02 -04:00			`sbinscripts_SCRIPTS = plymouth-set-default-theme`
Add new plymouth-set-default-plugin script This script updates which plugin graphical.so points to 2008-06-11 10:21:18 -04:00
Gut plymouth-update-initrd It's broken and people keep using it, so change it so that it's useful. 2008-10-17 15:49:31 -04:00			`EXTRA_DIST= plymouth-update-initrd \`
[scripts] Don't hardcode LIBEXECDIR and DATADIR paths The scripts hard-coded the paths for LIBEXECDIR and DATADIR, unless passed as environment variables. Instead of doing this, which breaks if plymouth is installed outside of /usr, set these derived from the configure $libexecdir and $datadir variables just as we do for pkg-config, etc. Since we use so many variables, it makes more sense to generate these scripts from config.status rather than having special Makefile rules for them. 2010-03-02 20:06:43 +00:00			`plymouth-generate-initrd.in \`
Don't ship pregenerated initrd scripts in tarball 2008-06-12 12:10:59 -04:00			`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) 2009-04-29 14:25:02 -04:00			`plymouth-set-default-theme.in \`
Don't ship pregenerated initrd scripts in tarball 2008-06-12 12:10:59 -04:00			`$(noinst_SCRIPTS) \`
			`default.cfg`