James Rayner wrote:
On Sun, November 4, 2007 04:25, Thomas Bächler wrote:
Jason Chu schrieb:
User has to install splashy or fbsplash which provide required mikinitcpio hooks and ${SPLASH}_wrapper script, and then use e.g. SPLASH="splashy" in rc.conf to enable it.
+1 from me. We either do the work here (and it doesn't break anything for the users who don't change a thing) or we have to fight with it later in a different package that's nearly exactly the same as initscripts with only a few changes.
I don't like certain details about the patch, but we should create a branch in the initscripts git to finalize it all and then apply it.
+1 from here.
+1 from me. Last I saw the patch was unintrustive and wasn't complicated at all.
The support is not activated by default, a user still needs to install splashy/fbsplash, etc.
I see no practical reason this patch should not be included. It has no negative side effects, offers more, and is not complicated.
Jamese
_______________________________________________ arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public
+1 from me too. I agree with James. I want a nice splash once I know my system is running ok, and I don't want to have to struggle to get it. I remember trying splash from community/Aur once long time ago, and since it borked my system, I never wanted to get back to it. If we provide some kind of official support, I'm assuming a good number of users would be interested. So +1 for NOT activating support by default, but making it easy to get if required. Varun