Personal tools
You are here: Home Development Rebranding Fedora with Revisor

Rebranding Fedora with Revisor

This is a short article on using Revisor to rebrand Fedora

About this document

This document is a DRAFT.

This document is not intended to show you how to completely rebrand Fedora. We're preparing to add the rebranding as a feature to Revisor, and as such, need some document to keep track of some things. You're looking at it. This document describes how Revisor could rebrand Fedora from it's existing code-base. It does not however tell you where you should replace logos and/or trademarks.

About Rebranding Fedora

When must one rebrand Fedora?

You can no longer call the product Fedora, if;

  1. you are to include any parts that Fedora doesn't ship, whether it be software, drivers or firmware, and
  2. you are going to distribute and/or publish the product in any way.

When can I say my distribution is derived from Fedora?

You can say your distribution is derived from Fedora if it remains to be using the genuine Fedora repositories (http://mirrors.fedoraproject.org/publiclist) and you haven't modified those in any particular way. This should enable you to override any set of packages Fedora ships, and ship extra packages that Fedora doesn't ship alongside with it.

Do I have to ship the source?

If you are distributing the product, you are obligated to also make the source available. If you're just using Fedora to compose your product (also called a Remix), Fedora already provides the sources and you can point there. If you are distributing the product and you had to rebrand Fedora in order to be able to do so, you are obligated to provide sources along with anything Fedora doesn't ship and that has the source available.

Though, are you including any parts that Fedora doesn't ship, whether it be software, drivers or firmware, just for your personal use, you do not need to rebrand Fedora (nor provide the sources to yourself).

Rebranding Fedora Legal Issues and Requirements

I guess there's some legal requirements:
  1. Remove fedora-logos
  2. Remove fedora-release?
  3. Remove fedora-release-notes?

So, I've rebuild the fedora-logos, fedora-release and fedora-release-notes packages, just as a proof of concept, to kanarip-logos, kanarip-release-8.0-1 and kanarip-release-notes-8.0.0. It has all the fedora-info though, so it isn't really rebranding, just a proof of concept.

Add them to the kickstart config you use to spin the model:

%packages
kanarip-logos
kanarip-release
kanarip-release-notes

And add a model to /etc/revisor/revisor.conf:

[k8-i386]
main = /etc/revisor/conf.d/revisor-k8-i386.conf
product_name = kanarip
product_path = kanarip
iso_basename = kanarip
comps = /etc/revisor/comps-f7.xml
architecture = i386
version = 8
getsource = 0
release_pkgs = ^kanarip-release.*$
release_files = eula.txt fedora.css GPL README-BURNING-ISOS-en_US.txt RELEASE-NOTES-en_US.html ^RPM-GPG img images stylesheet-images
#copy_dir = /data/test/etc/revisor
#strip_copy_dir = /data/test

And add the local repository with the kanarip-logos, kanarip-release and kanarip-release-notes in that repo (see the repo in bold):

[main]
cachedir=-yumcache
reposdir=
keepcache=0
debuglevel=1
logfile=/var/log/revisor-yum.log
pkgpolicy=newest
distroverpkg=kanarip-release
tolerant=1
exactarch=1
obsoletes=1
gpgcheck=1
plugins=0
metadata_expire=1800
installroot=/var/tmp/revisor

[fedora]
name=Fedora 7 - Moonshine - i386
#baseurl=http://localrepo/fedora/releases/7/Everything/i386/os/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-7&arch=i386
enabled=1
gpgcheck=0

[kanarip]
name=kanarip 8 - Sunshine - i386
# You can just leave this here, it works
baseurl=http://fedora.kanarip.com/custom/
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-7&arch=i386
enabled=1
gpgcheck=0


[updates]
name=Fedora 7 - i386 - Updates
#baseurl=http://localrepo/fedora/updates/7/i386/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f7&arch=i386
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora

Run revisor with that config end you'll end up with something like this

Some tests to see what is on the ISO

These are some tests to see what is on that ISO image.

[root@elwood ~]# mount -o loop -t iso9660 /srv/revisor/iso/kanarip-8-i386-CD.iso /mnt/k8/
[root@elwood ~]# cd /mnt/k8
[root@elwood k8]# ls -l
total 277
-rw-r--r-- 1 root root   2882 2007-06-26 15:00 fedora.css
-rw-r--r-- 1 root root  18385 2007-06-26 15:00 GPL
drwxr-xr-x 4 root root   2048 2007-06-26 15:00 images
drwxr-xr-x 2 root root   4096 2007-06-26 15:00 img
drwxr-xr-x 2 root root   2048 2007-06-26 14:56 isolinux
drwxr-xr-x 2 root root  65536 2007-06-26 14:53 kanarip
-rw-r--r-- 1 root root  10000 2007-06-26 15:00 README-BURNING-ISOS-en_US.txt
-rw-r--r-- 1 root root 157555 2007-06-26 15:00 RELEASE-NOTES-en_US.html
drwxr-xr-x 2 root root   2048 2007-06-26 14:53 repodata
-rw-r--r-- 1 root root   1910 2007-06-26 15:00 RPM-GPG-KEY
-rw-r--r-- 1 root root   1706 2007-06-26 15:00 RPM-GPG-KEY-beta
-rw-r--r-- 1 root root   1519 2007-06-26 15:00 RPM-GPG-KEY-fedora
-rw-r--r-- 1 root root   1105 2007-06-26 15:00 RPM-GPG-KEY-fedora-rawhide
-rw-r--r-- 1 root root   1076 2007-06-26 15:00 RPM-GPG-KEY-fedora-test
-rw-r--r-- 1 root root   1232 2007-06-26 15:00 RPM-GPG-KEY-rawhide
drwxr-xr-x 2 root root   4096 2007-06-26 15:00 stylesheet-images
-r--r--r-- 1 root root   4062 2007-06-26 15:00 TRANS.TBL
[root@elwood k8]# cd kanarip
[root@elwood kanarip]# ls *fedora*
ls: cannot access *fedora*: No such file or directory
[root@elwood kanarip]# ls *kanarip*
kanarip-logos-6.0.98-3.fc8.noarch.rpm  kanarip-release-8-1.noarch.rpm  kanarip-release-notes-8.0.0-1.noarch.rpm
Document Actions
Log in


Forgot your password?