I think those optional packages may give you much more work than just including the arch-stuff with standard packages, but i think you have a good reason to choose this way.
]]>Yeah, i also miss the Arch-splash screen. I understand that too much customization may difficult maintenance, but we also need some personality... i mean, the kernel has an arch logo, kde menu and so on. So everyone that watches our computer knows we're running Arch and not just a random distribution. Anyway, it would be nice to have the OOo arch splash screen back.
I will be putting together artwork-related packages over the next couple of weeks. I will include an OOo splash package that contains the logo mentioned above--it will be optional (e.g. not included with the default OOo package.)
]]>Not that I don't like the idea of it being applied to the package in the repo btw.
]]>there's no package for now.. i'm not trying to do a flame here but including a bmp file wouldn't increase the total work that much, would it ?
Not that I wouldn't like to have a branded OO, but this kind of argument can be applied to every individual patch, to every ... well, you get the idea.
]]>I'm not sure how things have change since then, but you should ask the OO.o package maintainer as to why your splash screen was not used for this release, T-u-N-i-X.
]]>