gensplash + qingy

言い出した手前，色々誤解の無い様に落ち穂拾い．
[Well, it's a followup.]

bootsplashとgensplashは別物．参考：spock's devsite gensplash::FAQ 1
genkernelの--gensplash=${THEME}には/etc/splash直下のディレクトリ名を指定．
genkernelの--gensplash=${WIDTH}x${HEIGHT}は適当な解像度のみを指定，
且つ，/etc/splash/${THEME}/${WIDTH}x${HEIGHT}.cfgが存在する事を確認．
[bootsplash isn't gensplash. see also: spock's devsite gensplash::FAQ 1
--gensplash=${THEME} as a genkernel's option requires directroy's name which is in under the /etc/splash.
--gensplash-res=${WIDTH}x${HEIGHT} as a genkernel's option requires to set sane resolution of your display, and then make sure that you have /etc/splash/${THEME}/${WIDTH}x${HEIGHT}.cfg.]

つまり，
genkernel経由で，
emergenceをテーマに使用して，
1024x768なgensplashを使う為には以下を実行．
[Therefore,
If you want to use genkernel, to use emergence as a theme of gensplash, your display resolution is 1024x768, then please do like that.]

 $ genkernel --menuconfig --gensplash=emergence --gensplash-res=1024x768 all

この時，--bootsplashオプションは必要有りません．
カーネルコンフィグ画面で，
CONFIG_FB_SPLASH=yになる様に設定するのを忘れずに．
既に，CONFIG_FB_SPLASH=yなら，最後のgenkernelコマンドは，
[So, --bootsplash as a option of genkernel is NOT mandatory with it.
When configuration the kernel, make sure to set CONFIG_FB_SPLASH=y.
If you already had like that setting, all you have to do is,]

 $ genkernel --oldconfig --gensplash=emergence --gensplash-res=1024x768 initrd

でinitramfsだけ作り直せばOK．
[for re-generate your initramfs.]

もちろん，カーネルのソースは，
gensplashに対応出来る様にfbsplashパッチが適用されていないとダメ．
ちなみに，このパッチはgentoo-sourcesには常に適用されているみたい．
他は適当に調べてくださいな．
initramfsが巧く作れれば，ブートローダが在れば何処でも使えるハズの
ブート時にカーネルに渡すパラメータの説明が出るので適当に設定して下さいな．
[Of cource, your kernel sources were patched with the fbsplash patch before you built the kenrel/initramfs.
sys-kernel/gentoo-sources seems be patched when it released.
If you use other kernel sources, you have to confirm whether it's patched.
Then, after to generate initramfs succesfully, you'll see some warning for using the gensplash with some boot-loader.
It's as known as kernel parameters for boot your kernel, so you have to set it.]

次はsys-apps/qingy．
コイツはdev-libs/DirectFBを使うので，何も考えずにやると危険です．
と言うのは，dev-libs/DirectFBが偶に後方互換性を切り捨てたりするので，
これにリンクされたアプリケーション，
つまり，USE="directfb"でemergeしたアプリケーションが固まったり，
fusionと言うカーネルモジュールをあわせて使う事も出来るので，
カーネルのアップグレード時にリコンパイルを忘れたりすると刺さるのです．
[Next is sys-apps/qingy.
It requires dev-libs/DirectFB, so some dangerousness are.
Like I said, dev-libs/DirectFB sometimes breaks its backward-comptibilities,
so some apps were linked with it will lock-up/break.
And then, it can use fusion as a kernel module.
So, If you forgot to re-compile it when upgrade the kernel,
your system will lock-up/break.]

なお，fusionカーネルモジュールは今のところ公式なPortageには入ってません．
よって，dev-libs/DirectFBをUSE="fusion"でemergeすると多分失敗します．
どうしてもUSE="fusion"なdev-libs/DirectFBが欲しい人は，
new ebuild: fusion for DirectFBを見てください．
ただし，sys-apps/qingyの為だけにdev-libs/DirectFBを使うのなら，
このfusionモジュールは必要ありません．
このfusionカーネルモジュールは，今のところ，
x11-base/{xdirectfb,XDirectFB}を使わない限り必要無いと思います．
更に，このfusionと言うUSEフラグ自体が，
profileによってはuse.maskされている事も有ります．
本当は動くのですが，ハマる人が多かった所為でppcではマスクされてます．
[Unfortunatlly, the fusion module is not contained in official portage tree at the moment.
So, it means that emerging dev-libs/DirectFB with USE="fusion" will have compilation failure at the moment.
If you want to emerge it with USE="fusion", please see new ebuild: fusion for DirectFB.
However, if you want to use dev-libs/DirectFB ONLY for sys-apps/qingy, it's NOT mandatory to emerge it with USE="fusion".
At the moment, the fusion module is ONLY required by x11-base/{xdirectfb,XDirectFB}.
And then, fusion as a USE flag may be masked by some profiles' use.mask for many packages' stabilities.
Of cource, the fusion module works fine on many architectures, IIRC.]

お薦めの設定としては，
/etc/make.confのUSEフラグに-directfb -fusionを入れておいて，
/etc/portage/package.useでdirectfbをUSEフラグに含むアプリケーションに対して，
どうしても必要ならONにして下さい．
最低限，
dev-libs/DirectFBにはUSE="fbcon gif png jpeg truetype zlib sysfs"が有れば，
sys-apps/qingyの為には十分なハズです．
後は，
/etc/inittab，
/etc/qingy以下のディレクトリ／ファイル，
/usr/share/qingy以下のディレクトリ／ファイル
辺りを適当に弄って下さい． :P
[I recommend to set USE="-directfb -fusion" in /etc/make.conf.
And, if you want to use the app with dev-libs/DirectFB, set directfb as a USE flag in /etc/portage/package.use.
At least, all you have to do for using sys-apps/qingy with dev-libs/DirectFB is to emerge dev-libs/DirectFB with USE="fbcon gif png jpeg truetype zlib sysfs", IIRC.
After emerge it, feel free to modify /etc/inittab, /etc/qingy, /use/share/qingy or so, AT YOUR OWN RISK. :P]