|
 |
e8ec7a |
---
|
|
|
e8ec7a |
title: "CentOS variants"
|
|
|
e8ec7a |
markdown: basic
|
|
|
e8ec7a |
is_dynamic: true
|
|
|
e8ec7a |
---
|
|
|
e8ec7a |
* Table of contents will replace this text.
|
|
|
e8ec7a |
{:toc}
|
|
|
e8ec7a |
|
|
|
e8ec7a |
|
|
|
e8ec7a |
#CentOS variants ( proposal )
|
|
|
e8ec7a |
|
|
|
e8ec7a |
A CentOS variant is a special edition of CentOS Linux that starts with the core distribution, then replaces or supplements a specific subset of packages. This may include replacing everything down to the kernel, networking, and other subsystems.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
The purpose of a variant edition is to allow another open source project to more effectively use CentOS as a base platform for running on and inside of.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
Some open source projects need different software components to run properly, such as updated development languages or kernel functionality. By being able to get these components directly in CentOS, a variant maintainer solves many of the steps for users.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
The end goal is to make it easier for users to run different open source software directly on and in CentOS itself.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
[Special interest groups](http://wiki.centos.org/SpecialInterestGroup) (SIGs) are teams of people interested in one or more related technologies, and enabling that technology in CentOS.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
These SIGs want to get this technology in the hands of the users in the easiest way possible. SIG members usually include people who work directly on the related technology and open source projects.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
(Some SIGs don't focus on producing a variant but instead work on Infrastructure, Design, Documentation, and so forth.)
|
|
|
e8ec7a |
|
|
|
e8ec7a |
#Using variants
|
|
|
e8ec7a |
|
|
|
e8ec7a |
It's as easy as using CentOS core. There are two main ways:
|
|
|
e8ec7a |
|
|
|
e8ec7a |
* Download a pre-built image [here](/download).
|
|
|
e8ec7a |
* Run the minimal installer from [here](/download) and choose your variant during installation.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
You may want to look for additional tips, notes, and documentation in the [SIG that produces the variant](http://wiki.centos.org/SpecialInterestGroup).
|
|
|
e8ec7a |
|
|
|
e8ec7a |
# Note:
|
|
|
e8ec7a |
|
|
|
e8ec7a |
The idea of CentOS Variants is very much a proposal at this stage, something we hope to have confirmed as a process and ensure we have resources allocated to make this happen by the early summer of 2014. However, if you are interested in joining the process right away, and dont mind being a part of the evolving process - feel free to drop a proposal for your variant onto the centos-devel list ( http://lists.centos.org/mailman/listinfo/centos-devel ) and we will try to include you in the process.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
Some potential early SIG's are listed on the [Special Interest Groups ](http://wiki.centos.org/SpecialInterestGroup)
|
|
|
e8ec7a |
|
|
|
e8ec7a |
#Making variants
|
|
|
e8ec7a |
|
|
|
e8ec7a |
An official variant edition of CentOS can only be created with code from git.centos.org, must be converted entirely from source to binary within the CentOS buildsystems and delivered using the official CentOS content delivery network.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
The gateway to code getting in to git.centos.org is via the SIGs. For example, the SIG that maintains a variant or the core SIG that builds the main CentOS distribution.
|
|
|
e8ec7a |
|
|
|
e8ec7a |
You may want to join an existing SIG or start a new one if you have an idea for a completely new variant. [Read more about starting a SIG](http://wiki.centos.org/SpecialInterestGroup).
|
|
|
e8ec7a |
|
|
|
e8ec7a |
Of course, you are always permitted to remix and redistribute the CentOS code, but you need to read the [trademark guidelines](/legal/trademarks/) to know if you can call it "CentOS".
|