Hi,

if we replace fedora-logos for generic-logos to try and re- or unbrand
Fedora, /etc/rc.sysinit gets in the way:


==
# Print a text banner.
echo -en $" Welcome to "
read -r redhat_release < /etc/redhat-release
if [[ "$redhat_release" =~ "Red Hat" ]]; then
[ "$BOOTUP" = "color" ] && echo -en "33[0;31m"
echo -en "Red Hat"
[ "$BOOTUP" = "color" ] && echo -en "33[0;39m"
PRODUCT=`sed "s/Red Hat (.*) release.*/1/" /etc/redhat-release`
echo " $PRODUCT"
elif [[ "$redhat_release" =~ "Fedora" ]]; then
[ "$BOOTUP" = "color" ] && echo -en "33[0;34m"
echo -en "Fedora"
[ "$BOOTUP" = "color" ] && echo -en "33[0;39m"
PRODUCT=`sed "s/Fedora (.*) ?release.*/1/" /etc/redhat-release`
echo " $PRODUCT"
else
PRODUCT=`sed "s/ release.*//g" /etc/redhat-release`
echo "$PRODUCT"
fi
==

Resulting in "Welcome to Fedora" when a machine boots -both Live Media
and Installation media.


No biggy, but I'm not sure whether replacing the contents of
/etc/fedora-release (from fedora-release) would give my any trouble, and
if so, whether we need to replace fedora-release when rebranding as well.


Another approach is to modify rc.sysinit in a way that takes into
account rebranding.


Another approach is to move /etc/*-release to fedora-logos and having a
generic-logos alternative.


I'd like some additional thoughts on this and some advice on what to pursue.

Kind regards,

Jeroen van Meeuwen
-kanarip

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Jeroen van Meeuwen (kanarip@kanarip.com) said:
> Resulting in "Welcome to Fedora" when a machine boots -both Live Media
> and Installation media.
>
> No biggy, but I'm not sure whether replacing the contents of
> /etc/fedora-release (from fedora-release) would give my any trouble, and
> if so, whether we need to replace fedora-release when rebranding as well.

The idea is that if you're adding packages, etc., you'd be pointing
at your own repos, in which case you already want to modify *-release.

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Bill Nottingham <notting <at> redhat.com> writes:
> The idea is that if you're adding packages, etc., you'd be pointing
> at your own repos, in which case you already want to modify *-release.

Not necessarily. It is usually enough to add a *-release file, without
modifying fedora-release. Even if you modify some packages, you can easily
override Fedora's versions e.g. by using Epochs.

Kevin Kofler

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Bill Nottingham wrote:
Jeroen van Meeuwen (kanarip@kanarip.com) said:
Resulting in "Welcome to Fedora" when a machine boots -both Live Media
and Installation media.


No biggy, but I'm not sure whether replacing the contents of
/etc/fedora-release (from fedora-release) would give my any trouble, and
if so, whether we need to replace fedora-release when rebranding as well.


The idea is that if you're adding packages, etc., you'd be pointing
at your own repos, in which case you already want to modify *-release.



This problem is the case where you just want to rebrand, not including
other packages or doing anything non-Fedora. For example, live spins
that have not been approved by the Board yet, will want to:


%packages
-fedora-logos
+generic-logos
%end

and the machine booting the live media would still show "Welcome to
Fedora". Can one safely do:


%post
sed -i -e "s/Fedora/Generic/g" /etc/fedora-release
%end

?

Kind regards,

Jeroen van Meeuwen
-kanarip

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Kevin Kofler wrote:

Bill Nottingham <notting <at> redhat.com> writes:

The idea is that if you're adding packages, etc., you'd be pointing
at your own repos, in which case you already want to modify *-release.


Not necessarily. It is usually enough to add a *-release file, without
modifying fedora-release. Even if you modify some packages, you can easily
override Fedora's versions e.g. by using Epochs.




One could add other *-release RPMs, yeah. Those could just install the
RPM GPG keys and .repo files -and be done with it. There'd be rebranding
involved but it wouldn't force one to not use the Fedora repositories on
such a system.


Having to provide capability 'system-release', possibly with a higher
nevra, is what I'd call "replacing the fedora-release package" as
opposed to just replacing 'fedora-logos', which would mean a challenge
for the users attempting rebranding/debranding.


Kind regards,

Jeroen van Meeuwen
-kanarip

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Jeroen van Meeuwen (kanarip@kanarip.com) said:
> %post
> sed -i -e "s/Fedora/Generic/g" /etc/fedora-release
> %end

Works for me as a special case; I think redoing another -release package
is probably overkill.

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list