Documentation discussion

Moray Henderson Moray.Henderson at ict-software.org
Tue Apr 17 13:37:56 UTC 2012


> From: Chris Tyler [mailto:chris at tylers.info]
> Sent: 16 April 2012 16:12
> 
> On Mon, 2012-04-16 at 16:05 +0100, Moray Henderson (ICT) wrote:
> > I spotted a couple of points where I think the Koji documentation
> could be
> > improved:
> 
> It's a wiki, edits accepted :-)

I would expect that edits are more accepted when they come from someone who knows what they're talking about, though.  I want to the documentation made better, not worse ;-)

If I did it, these are the changes I would make.  If they're right, let me know and I'll apply for a Fedora Account and make them.


--- ServerHowTo.1.txt   2012-04-17 14:13:56.000000000 +0100
+++ ServerHowTo.2.txt   2012-04-17 14:15:39.000000000 +0100
@@ -511,7 +511,7 @@
 Add the host entry for the koji builder to the database
 You will now need to add the koji builder to the database so that they can be utilized by kojij hub. Make sure you do this before you start kojid for the first time, or you'll need to manually remove entries from the sessions and users table before it can be run successfully.

-kojiadmin at localhost$ koji add-host kojibuilder1.example.com i386 x86_64
+kojiadmin at localhost$ koji add-host kojibuilder1 i386 x86_64
 The first argument used after the add-host command should the username of the builder. The second argument is used to specify the architecture which the builder uses.

 Add the host to the createrepo channel
--- ExternalRepoServerBootstrap.1.txt   2012-04-17 14:16:23.000000000 +0100
+++ ExternalRepoServerBootstrap.2.txt   2012-04-17 14:16:58.000000000 +0100
@@ -31,12 +31,12 @@
 all these examples use mirrors.kernel.org please find the closest mirror to yourself. Note that the Fedora minimal buildroots download ~100Mb then build dependencies on top. these are downloaded each build you can save alot of network bandwidth by using a local mirror or running through a caching proxy.

 Fedora 10
-http://mirrors.kernel.org/fedora/releases/10/Everything/\$arch/os/
 http://mirrors.kernel.org/fedora/updates/10/\$arch/
+http://mirrors.kernel.org/fedora/releases/10/Everything/\$arch/os/
 CentOS 5 and EPEL
-http://mirrors.kernel.org/centos/5/os/\$arch/
-http://mirrors.kernel.org/centos/5/updates/\$arch/
 http://mirrors.kernel.org/fedora-epel/5/\$arch/
+http://mirrors.kernel.org/centos/5/updates/\$arch/
+http://mirrors.kernel.org/centos/5/os/\$arch/
 Example tags and targets
 In the simplest setup, where you just want to build against what is available in the external repositories, you may want to go with a simple layout of dist-fX-build tags inheriting one another, and dist-fX-updates tags and targets that inherit the dist-fX-build tag and have external repos attached to them. This way, a dist-fY-build or dist-fY-updates tag will not automatically inherit the external repos of your dist-fX tags.



Moray.
“To err is human; to purr, feline.”







More information about the buildsys mailing list