[CentOS] How can a company help, officially?

[Johnny Hughes]

On 04/12/2011 06:58 AM, Karanbir Singh wrote:
> On 04/12/2011 12:48 PM, Radu Gheorghiu wrote:
>>> There are pages in the wiki that already describe what we are doing
>>> right now.
>> I think you already stated that the pages about rebuilding are outdated.
> 
> Thats not what was said : we might not be using the exact same scripts 
> is more along the lines of what was said. But yes, there is some level 
> of scope to gather the info from various places into a single place. 
> Quite a lot things are scattered around and need people to make an 
> effort. Having a single starting page, as it were, would help.
> 
> A couple of days back, someone offered to start that process off. I will 
> help alongside as much as I can.
> 
>> Useless unless I can replicate your build system. We must work on the
>> same thing, not on separate things.
> 
> Ok, so that's a much more tangible question! Replicating the build 
> system isn't hard. Its almost a case of doing a for loop with mock and 
> looking at results of what that turns out. This question has been 
> answered at-least a few dozen times in recent past. Look at mock, look 
> at yum and make sure you understand spec files.
> 
> But remember, that building packages is only a small part of what we are 
> doing.

I have posted again and again example scripts that we use.

We use mock to build packages ... specifically, we use the mock released
in CentOS Extras for CentOS 5 to build packages.

Some people keep asking for our mock config files.  I gave examples of
those (centos-5-i386-os-ft-extrasStaged.cfg,
centos-5-x86_64-os-ft-extrasStaged.cfg).  They are not rocket science.
If you point to the [base] and [updates] directory for CentOS for the
thing you are trying to build, then you have it.  If you are building
extras, add in [extras].  If you are building CentOSPlus, add in
[centosplus].  If I provide you the exact file, it does not help.  It
points to names we do not want to give out because we do not want our
internal names to published for security reasons, but we quite simply
use [os] and [updates] to build the main OS, and other repos as
necessary to build [extras] or [centosplus].  Point to ONLY the CentOS
repos, we do not pull in any other items for our builds. If we need a
package (in extras or centosplus) then we add it.

We do staged builds (that means when we get a good build, it goes into
the build tree).  I gave examples of scripts that do that
(cp_extrasStaged_live).

We test the RPMs against upstream RPMs.  I gave a script of that
(tmverifyrpms).

When we have a tree of RPMS, we build the "distro tree".  I gave an
example of that too.  (build.sh.txt).

All of the files I talked about in this post are either here:

http://people.centos.org/hughesjr/buildsystem/

or here:

http://mirror.centos.org/centos-4/4/build/distro/

Also included are actual buildscripts for an ExtrasStaged repo
(buildpackages_mock_c5_extrasStaged_i386,
buildpackages_mock_c5_extrasStaged_x86_64) and a script that "generates"
the order to build packages based on their previous build date
generaterpmlist().

All of this is also linked from here:

http://wiki.centos.org/FAQ/General/RebuildReleaseProcess

The point here is that we are not going to share access to our actual
build system and we are not going to give you our actual build scripts
off that system as they use names that we do not want to publish and
contain files that we can not allow people to have access to.  But these
example scripts give someone who wants to build their own items the
starting point that they need to do that.

Thanks,
Johnny Hughes

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos/attachments/20110412/b66b38e6/attachment.sig>