|
|
f11ee4 |
@subheading Goals
|
|
|
f11ee4 |
|
|
|
f11ee4 |
This section organizes default design models for different major
|
|
|
f11ee4 |
releases of CentOS Distribution.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
@subheading Description
|
|
|
f11ee4 |
|
|
|
f11ee4 |
In order to better understatand how this visual manifestation is
|
|
|
f11ee4 |
organized, it is necessary to consider what The CentOS Distribution is
|
|
|
f11ee4 |
and how it is released.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
@subsubheading The CentOS Distribution
|
|
|
f11ee4 |
|
|
|
f11ee4 |
The CentOS Distribution is an Enterprise-class Linux Distribution
|
|
|
f11ee4 |
derived from sources freely provided to the public by a prominent
|
|
|
f11ee4 |
North American Enterprise Linux vendor. The CentOS Distribution
|
|
|
f11ee4 |
conforms fully with the upstream vendors redistribution policy and
|
|
|
f11ee4 |
aims to be 100% binary compatible. (The CentOS Project mainly changes
|
|
|
f11ee4 |
packages to remove upstream vendor branding and artwork.)
|
|
|
f11ee4 |
|
|
|
f11ee4 |
The CentOS Distribution is developed by a small but growing team of
|
|
|
f11ee4 |
core developers. In turn the core developers are supported by an
|
|
|
f11ee4 |
active user community including system administrators, network
|
|
|
f11ee4 |
administrators, enterprise users, managers, core Linux contributors
|
|
|
f11ee4 |
and Linux enthusiasts from around the world.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
@subsubheading The CentOS Distribution Release Schema
|
|
|
f11ee4 |
|
|
|
f11ee4 |
The upstream vendor has released 4 versions of their
|
|
|
f11ee4 |
@acronym{EL,Enterprise Linux} product that The CentOS Project rebuilds
|
|
|
f11ee4 |
the freely available SRPMS for. The upstream vendor releases security
|
|
|
f11ee4 |
updates as required by circumstances. The CentOS Project releases
|
|
|
f11ee4 |
rebuilds of security updates as soon as possible. Usually within 24
|
|
|
f11ee4 |
hours (our stated goal is with 72 hours, but we are usually much
|
|
|
f11ee4 |
faster).
|
|
|
f11ee4 |
|
|
|
f11ee4 |
The upstream vendor also releases numbered update sets for major
|
|
|
f11ee4 |
versions of their EL product from 2 to 4 times per year. There are new
|
|
|
f11ee4 |
ISOs from the upstream vendor provided for these update sets. Update
|
|
|
f11ee4 |
sets will be completed as soon as possible after the upstream vendor
|
|
|
f11ee4 |
releases their version @dots{} generally within 2 weeks. The CentOS
|
|
|
f11ee4 |
Project follows these conventions as well, so CentOS-3.9 correlates
|
|
|
f11ee4 |
with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6,
|
|
|
f11ee4 |
CentOS-5.1 correlates to EL 5 update 1, etc.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
One thing some people have problems understanding is that if you have
|
|
|
f11ee4 |
any CentOS-3 product and update it, you will be updated to the latest
|
|
|
f11ee4 |
CentOS-3.x version.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4
|
|
|
f11ee4 |
product, you will be updated to the latest CentOS-4.x version, or to
|
|
|
f11ee4 |
the latest CentOS-5.x version if you are updating a CentOS-5 system.
|
|
|
f11ee4 |
This is exactly the same behavior as the upstream product. Let's
|
|
|
f11ee4 |
assume that the latest EL4 product is update 6. If you install the
|
|
|
f11ee4 |
upstream original EL4 CDs (the ones before any update set) and upgrade
|
|
|
f11ee4 |
via @command{yum}, you will have latest update set installed (EL4
|
|
|
f11ee4 |
update 6 in our example). Since all updates within a major release
|
|
|
f11ee4 |
(CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest
|
|
|
f11ee4 |
version when updates are performed (thus mimicking upstream behavior),
|
|
|
f11ee4 |
only the latest version is maintained in each main tree on The CentOS
|
|
|
f11ee4 |
Mirrors (@url{http://mirrors.centos.org/}).
|
|
|
f11ee4 |
|
|
|
f11ee4 |
There is a CentOS Vault (@url{http://vault.centos.org/}) containing
|
|
|
f11ee4 |
old CentOS trees. This vault is a picture of the older tree when it
|
|
|
f11ee4 |
was removed from the main tree, and does not receive updates. It
|
|
|
f11ee4 |
should only be used for reference.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
The CentOS Distribution visual style is controlled by image files.
|
|
|
f11ee4 |
These image files are packaged inside The CentOS Distribution and made
|
|
|
f11ee4 |
visible once such packages are installed and executed. The way to go
|
|
|
f11ee4 |
for changing The CentOS Distribution visual style is changing all
|
|
|
f11ee4 |
those image files to add the desired visual style first and later,
|
|
|
f11ee4 |
repackage them to make them available inside the final iso files of
|
|
|
f11ee4 |
CentOS Distribution.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
@subheading Usage
|
|
|
f11ee4 |
|
|
|
f11ee4 |
Sometimes, between major releases, image files inside packages can be
|
|
|
f11ee4 |
added, removed or just get the name changed. In order to describe such
|
|
|
f11ee4 |
variations, the design models directory structure is organized in the
|
|
|
f11ee4 |
same way the variations are introduced (i.e., through The CentOS
|
|
|
f11ee4 |
Distribution Release Schema). So, each major release of The CentOS
|
|
|
f11ee4 |
Distribution has its own design model directory structure.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
When a new package/component is added to one or all the major releases
|
|
|
f11ee4 |
of The CentOS Distribution, a design model directory structure for
|
|
|
f11ee4 |
that component needs to be created. Later, it is filled up with
|
|
|
f11ee4 |
related design models. Design models are created for each image file
|
|
|
f11ee4 |
inside the component that need to be rebuilt in order to set the
|
|
|
f11ee4 |
visual style and brand information correctly.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
When a package is removed from one or all major releases of The CentOS
|
|
|
f11ee4 |
Distribution, the design model directory structure releated to that
|
|
|
f11ee4 |
package/component is no longer used. However, it could be very useful
|
|
|
f11ee4 |
for historical reasons. Also, someone could feel motivation enough to
|
|
|
f11ee4 |
keep himself documenting it or supporting it for whatever reason.
|
|
|
f11ee4 |
|
|
|
f11ee4 |
@itemize
|
|
|
f11ee4 |
@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro
|
|
|
f11ee4 |
5) ---.
|
|
|
f11ee4 |
@end itemize
|
|
|
f11ee4 |
|
|
|
f11ee4 |
@subheading See also
|
|
|
f11ee4 |
|
|
|
f11ee4 |
@itemize
|
|
|
f11ee4 |
@item --- @strong{Removed}(ref:Directories trunk Identity Models Themes Default) ---.
|
|
|
f11ee4 |
@item @ref{Directories trunk Identity Models Themes}.
|
|
|
f11ee4 |
@item @ref{Directories trunk Identity Images Themes}.
|
|
|
f11ee4 |
@item @ref{Directories trunk Identity}.
|
|
|
f11ee4 |
@item @ref{Directories trunk}.
|
|
|
f11ee4 |
@end itemize
|