Bill Nottingham wrote:
Rahul Sundaram (sundaram(a)fedoraproject.org) said:
>> It pulls the information from /etc/fedora-release - there's nothing to
>> do in plymouth itself. If your /etc/fedora-release comes from a correctly
>> rebranded package, the right thing should happen.
> Well, here is the thing. I run sed on /etc/fedora-release, I get a
> rebranded distro everywhere except for plymouth which already has picked
> up the name and won't let it go. Now I did replace fedora-release with
> my own foo-release but then I realized, I have to maintain my own
> repository now as well inorder to not break the upgrade path. I would
> like to avoid doing that by just not having Plymouth display that text
> at all.
Running 'sed' on distribution provided files seems like a bad way
to go about it. What if fedora-release gets updated upstream?
That has never happened really. I would like to avoid introducing my own
packages into the compose as much as possible and this seems to be the
best way to do it but I would take any good suggestions.
(That being said, you could certainly do a trigger to do the sed
at the right point after the package gets installed.)
I tried that and Plymouth still displays the old text when booting up as
a live cd and only gets the new text, post installation. If you figure
out a way to do it, let me know. I tried a few things and never managed
to get it right.