Permalink
Browse files

reworked most of the website - home, faq, packaging (all 3), header a…

…nd footer.
  • Loading branch information...
1 parent ea33fde commit a1cb5bff1a0d6b0e847ca86068ff099949560767 @PaulReiber PaulReiber committed with zyv Aug 17, 2012
Showing with 83 additions and 69 deletions.
  1. +1 −1 _includes/footer.html
  2. +3 −3 _layouts/default.html
  3. +39 −32 faq/index.md
  4. +10 −4 index.md
  5. +13 −13 package/index.md
  6. +5 −5 package/quickstart.md
  7. +12 −11 package/rebuild.md
@@ -1,4 +1,4 @@
<footer>
- <p> Help upgrade this website. Grab <a href="http://github.com/repoforge/repoforge.github.com/" title="The source code for this site.">the source code</a> and hack away. </p>
+ <p><a href="http://github.com/repoforge/repoforge.github.com/" title="github project for this website">help improve this website </a> | <a href="http://lists.repoforge.org/mailman/listinfo">get involved - join our mailinglists</a></p>
</footer>
@@ -20,12 +20,12 @@
<header class='span-24'>
<h1><a href="/" title="RepoForge">RepoForge</a></h1>
- <p id='tagline'>RepoForge is the new name of the RPMForge project.</p>
+ <p id='tagline'>RPMForge is now RepoForge.</p>
<nav>
<ul>
<li><a href="/">home</a></li>
- <li><a href="/use">users</a></li>
- <li><a href="/package">packagers</a></li>
+ <li><a href="/use">usage</a></li>
+ <li><a href="/package">packaging</a></li>
<li><a href="/faq">faq</a></li>
</ul>
</nav>
View
@@ -1,35 +1,37 @@
---
layout: default
-title: Repoforge FAQ
+title: RepoForge FAQ
---
-## Repoforge FAQ ##
+## RepoForge FAQ ##
-### What is Repoforge? ###
+### What is RepoForge? ###
-Repoforge is the new name of the RPMForge project.
+The RepoForge project maintains RPM packages for Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux. It provides a set of repositories compatible with various RHEL-derived distributions.
-Repoforge is a project that maintains RPM packages for Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux. It consists of a set of repositories compatible with various RHEL-derived distributions.
+### How do I use RepoForge? ###
-### How do I use this? ###
-
-See the [user guide](/use "user guide")
+See [Using RepoForge](/use "Using RepoForge")
### How can I contribute? ###
-* Become a [packager](/package "repoforge contributor") by fixing or adding new packages.
-* Get forking. Fork the repository you want to assist with, fix things, submit pull requests: _like [this website](http://github.com/repoforge/repoforge.github.com/)_.
-* Setup a new mirror of Repoforge. See below for the details.
+There are numerous ways you can help. Feel free to do more than one!
+* promote RepoForge - let people know when it helped you solve a problem.
+* Get active on [our mailinglists](http://lists.repoforge.org/mailman/listinfo)
+* Test the various packages in the repos, and let the package maintainers know about any problems you find
+* Become a [packager](/package "RepoForge contributor") by fixing packages or adding new packages.
+* Get forking. Fork the repository you want to assist with, fix things, submit pull requests: _for example, for the package that is [this website](http://github.com/RepoForge/RepoForge.github.com/)_.
+* Become a Mirror! You can setup a mirror of RepoForge - more details on that below.
### Why are there now several repositories? What is "rfx"? ###
Our goal is to move all packages that conflict with upstream packages into a separate "extras" repository; this way, users who want to be confident that our packages will not cause conflicts with upstream can enable the base repository, and users who want newer versions of packages (and are willing to tolerate some package conflicts) can enable the extras repository.
-More information is in [this post](http://lists.repoforge.org/pipermail/users/2010-November/018282.html).
+More information is in [this post](http://lists.RepoForge.org/pipermail/users/2010-November/018282.html).
-### How to become a mirror for Repoforge? ###
+### How to become a mirror for RepoForge? ###
-#### Requirements ####
+#### Mirror Requirements ####
We have a few requirements for those wishing to run a mirror:
1. You must subscribe to the mailing list for mirror maintainers.
@@ -40,49 +42,54 @@ We have a few requirements for those wishing to run a mirror:
6. You must do an update-check at least once a day, and preferably four times a day.
7. Do not rsync more rapidly than every hour.
8. Sync on a random minute so it is more likely the requests will be spaced out with other mirrors.
-9. You must use 'repoforge' name for the mirror.
+9. You must use 'RepoForge' name for the mirror.
#### Mirroring techniques ####
We only support rsync for updating mirrors. You can find details on rsync at http://rsync.samba.org/. Update your mirror with:
- /usr/bin/rsync -vai4CH --safe-links --delay-updates --delete rsync://a_Tier1_RepoForge_mirror/repoforge/ /path/to/local/mirror/repoforge
+ /usr/bin/rsync -vai4CH --safe-links --delay-updates --delete rsync://a_Tier1_RepoForge_mirror/RepoForge/ /path/to/local/mirror/RepoForge
We highly recommend the use of a lock file in your cron script, so that you do not spawn multiple connections, which is hard on our servers and on your mirror. Update your mirror with:
- /usr/bin/flock -w 60 /var/lock/EUAK1qEPB3SM /usr/bin/rsync -vai4CH --safe-links --delay-updates --delete rsync://a_Tier1_RepoForge_mirror/repoforge/ /path/to/local/mirror/repoforge
+ /usr/bin/flock -w 60 /var/lock/EUAK1qEPB3SM /usr/bin/rsync -vai4CH --safe-links --delay-updates --delete rsync://a_Tier1_RepoForge_mirror/RepoForge/ /path/to/local/mirror/RepoForge
Create your unique lockfile with:
cat /dev/urandom | tr -dc [:alnum:] | head -c12; echo
-#### Inform us ####
-Once the site is configured, tested, and updating consistently, you should subscribe to the mirror maintainers mailing list.
+#### After I setup a mirror, what next? ####
-Provide us with details of your mirror:
+You will need to INFORM us of your new mirror. Once the site is configured, tested, and updating consistently, you should subscribe to the mirror maintainers mailing list.
+Provide us with details of your mirror:
* URL of mirror
* Supported access methods (http, ftp, rsync, ...)
* Country / state / city where the mirror is located
* Contact email address
* Update frequency
* Approximate bandwidth
* The name of **Tier1** mirror you are syncing from, which should be one of these:
- - Asia:
-
- + **ftp.riken.jp** (Japan) - *rsync://ftp.riken.jp/repoforge/*
-
- - Europe:
-
- + **mirror1.hs-esslingen.de** (Germany) - *rsync://mirror1.hs-esslingen.de/repoforge/*
-
- + **repository.vsb.cz** (Czech Republic) - *rsync://repository.vsb.cz/repoforge/*
+
+ * Asia:
+
+ **ftp.riken.jp** (Japan) - *rsync://ftp.riken.jp/RepoForge/*
- - North-America / South-America:
+ * Europe:
+
+ **mirror1.hs-esslingen.de** (Germany) - *rsync://mirror1.hs-esslingen.de/RepoForge/*
+
+ **repository.vsb.cz** (Czech Republic) - *rsync://repository.vsb.cz/RepoForge/*
- + **repoforge.eecs.wsu.edu** (United States) - *rsync://repoforge.eecs.wsu.edu/repoforge/*
+ * North-America / South-America:
+
+ **RepoForge.eecs.wsu.edu** (United States) - *rsync://RepoForge.eecs.wsu.edu/RepoForge/*
Notes:
* If/when your mirror is on the list, you can change the IP of the mirror without notifying us.
-* If the best contact point for your mirror is not the address you are subscribed to the [mailing list](http://lists.repoforge.org/mailman/listinfo/mirrors) with, please provide the email address of your preferred contact as well.
+* If the best contact point for your mirror is not the address you are subscribed to the [mailing list](http://lists.RepoForge.org/mailman/listinfo/mirrors) with, please provide the email address of your preferred contact as well.
* Please alert the mailing list if anything about the server changes like location, available bandwidth, frequency of updates, etc.
+
+### Why is this FAQ so short? ###
+
+Because you have yet to [fork it on GitHub](http://github.com/RepoForge/RepoForge.github.com/) to add other questions/answers.
View
@@ -4,13 +4,19 @@ title: RepoForge Project
---
## Welcome to RepoForge! ##
+_RepoForge is the new RPMforge. Please excuse the dust as we move in and remodel._
-_This is the new home for the RepoForge project and still mostly a skeleton_
+The RepoForge project maintains RPM packages for:
+* Red Hat Enterprise Linux (RHEL)
+* CentOS
+* Scientific Linux.
-RepoForge is a project that maintains RPM packages for Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux. It consists of a set of repositories compatible with various RHEL versions.
+We provide a set of repositories compatible with various RHEL versions, providing packages for:
+ - Servers _(eg. monitoring, troubleshooting, management)_
+ - Desktops _(eg. office, leisure, multi-media)_
+ - Development _(eg. perl, python, ruby libraries)_
-
-Coming soon:
+For more information please see:
* [faq](/faq "repoforge faq") - some questions, some answers
* [using](/use "install repoforge") - Configure your system for RepoForge.
View
@@ -1,27 +1,27 @@
---
layout: default
-title: Contribute Packages
+title: Building and Contributing Packages
---
-[BuildSystem](quickstart.html) | [Rebuild](rebuild.html)
+[Contribute](index.html) | [BuildSystem](quickstart.html) | [Rebuilding](rebuild.html)
-## Contribute Packages ##
-
-RepoForge welcomes contributions! To contribute a new package, or a fix to an existing package, use the following procedure:
+## Contributing New Packages ##
+RepoForge welcomes contributions!
+To contribute a new package, or a fix to an existing package, use the following procedure:
1. Create an account on [GitHub](https://github.com/).
-
2. [Fork](http://help.github.com/fork-a-repo/) our [git repository](https://github.com/repoforge/rpms).
-
3. Make changes and commit them to your fork. See [BuildSystem](quickstart.html) for details on setting up a good build environment.
-
4. Submit a [pull request](http://help.github.com/pull-requests/) when your contribution is ready.
+## Follow the community ##
+
+* [Subscribe to the mailing list(s)](http://lists.repoforge.org/mailman/listinfo) - and of course, review the archives
+* Some of us hang out on #repoforge on irc.freenode.net
+* a bugtracker for RepoForge is in the works as well!
-### Follow the community ###
+## Building and Rebuilding ##
-* TODO: mailing list info
-* TODO: bug tracker
-* #repoforge on irc.freenode.net
+[BuildSystem](quickstart.html) provides a Quick Start guide for doing builds.
-Check out the [Rebuild Howto](/package/rebuild.html) for just rebuilding a single package.
+Check out the [Rebuild Howto](rebuild.html) for just rebuilding a single package.
View
@@ -2,14 +2,15 @@
layout: default
title: quick start
---
+[Contribute](index.html) | [BuildSystem](quickstart.html) | [Rebuilding](rebuild.html)
-# Quick Start build system
+## Quick Start build system ##
You want to spin out some fancy RepoForge action yourself. Test rebuilding SPEC files before asking for a pull request perhaps. Here is a quick start guide with the possible commands you might run:
* Spin out a new RHEL/CentOS machine
-> KVM is your friend if you don't have a spare physical box.
+ > KVM is your friend if you do not have a spare physical box.
* Software development tools
@@ -25,7 +26,7 @@ You want to spin out some fancy RepoForge action yourself. Test rebuilding SPEC
useradd -G mock repoforge
sudo -u repoforge -i
-* Checkout the RepoForge RPMs repository (or make & checkout your own fork if you are expecting to submit your patches back to us, which you really ought to, of course!)
+* Checkout the RepoForge RPMs repository (or fork our repo, & checkout your own fork - especially if you plan to submit patches back to us)
git clone git://github.com/repoforge/rpms.git
@@ -47,7 +48,6 @@ You want to spin out some fancy RepoForge action yourself. Test rebuilding SPEC
* Paste the following contents
#!/bin/bash
-
rpmbuild \
--define "_source_filedigest_algorithm 1" \
--define "_binary_filedigest_algorithm 1" \
@@ -64,4 +64,4 @@ You want to spin out some fancy RepoForge action yourself. Test rebuilding SPEC
rpmbuild-old -bs file.spec
-For people serious about doing a good job: build and test at least on RHEL4, RHEL5 and RHEL6 by specifying correct config files to mock builder!
+> For those serious about doing a good job - build and test at least on RHEL4, RHEL5 and RHEL6 by specifying correct config files to mock builder
View
@@ -2,38 +2,39 @@
layout: default
title: Manual Rebuild
---
+[Contribute](index.html) | [BuildSystem](quickstart.html) | [Rebuilding](rebuild.html)
## Manually rebuilding a package from RepoForge ##
-So, maybe you've requested that a package be added to RepoForge, and a maintainer has written back to you something like "I've committed your package; it'll be available once it's rebuilt." You may be thinking "But... How long will that take? I need this now!"
+So, maybe you have requested that a package be added to RepoForge, and a maintainer has written back to you something like "I've committed your package; it'll be available once it's rebuilt." You may be thinking "But... How long will that take? I need this now!"
-Alternately, perhaps like [this guy](http://comments.gmane.org/gmane.linux.centos.general/96029) you've discovered that shared libraries have changed under your feet, and a package no longer works, and people say things like "just rebuild it".
+Alternately, perhaps like [this guy](http://comments.gmane.org/gmane.linux.centos.general/96029) you have discovered that shared libraries have changed under your feet, and a package no longer works, and people say things like "just rebuild it".
-One workaround for situations like these is to manually rebuild the package; I'll step you through this process.
+One workaround for situations like these is to manually rebuild the package:
### Set up your environment ###
-First, make sure your system is configured to pull packages from RepoForge. If you haven't already done so, install the latest rpmforge-release package for your distribution and architecture.
+First, make sure your system is configured to pull packages from RepoForge. If you have not already done so, install the latest rpmforge-release package for your distribution and architecture.
Next, make sure you have development tools installed. The most straightforward way to do this is the following command:
$ sudo yum groupinstall "Development Tools"
-In addition, you'll want the following packages:
+In addition, you will want the following packages:
$ sudo yum install rpm-build rpm-macros-rpmforge spectool yum-utils
-Finally, set up your environment such that you can build RPMs as a non-root user. Russ Herrold has written [a detailed guide](http://www.owlriver.com/tips/non-root/); the parts relevant to this step are parts 2, 3, and 4. For the rest of this document, I'll assume that you've set up your build directories as directed by Russ.
+Finally, set up your environment such that you can build RPMs as a non-root user. Russ Herrold has written [a detailed guide](http://www.owlriver.com/tips/non-root/); the parts relevant to this step are parts 2, 3, and 4. For the rest of this document, I will assume that you have set up your build directories as directed by Russ.
### Download the package to be rebuilt ###
-Determine whether this package is a brand new, never-before-built package (as in the first example at the top of the page) or whether you're rebuilding an existing package (as in the second example). If you're rebuilding an existing package, the process is easier, since you'll have access to a SRPM; if you're rebuilding a brand new package, all you'll have is the specfile.
+Determine whether this package is a brand new, never-before-built package (as in the first example at the top of the page) or whether you are rebuilding an existing package (as in the second example). If you are rebuilding an existing package, the process is easier, since you will have access to an SRPM; if you are rebuilding a brand new package, all you will have is the specfile.
### Rebuilding a SRPM ###
Browse to http://packages.sw.be/ and download the SRPM for the desired package version. SRPMs are packages with names ending in .src.rpm.
-Once you've downloaded the SRPM, make sure you have all the necessary dependencies to build it:
+Once you have downloaded the SRPM, make sure you have all the necessary dependencies to build it:
$ sudo yum-builddep <package>.src.rpm
@@ -43,7 +44,7 @@ Once you have the SRPM and all its dependencies installed, run the following com
$ rpmbuild --rebuild <package>.src.rpm
-You'll see a lot of output; if the process completes successfully, you'll see that among the last of the status messages are lines telling you where rpmbuild has put your newly build RPMs. Here's an example from a build of the rabbitvcs package:
+You will see a lot of output; if the process completes successfully, you will see that among the last of the status messages are lines telling you where rpmbuild has put your newly build RPMs. Here is an example from a build of the rabbitvcs package:
...
Checking for unpackaged file(s): /usr/lib/rpm/check-files /tmp/rpmbuild/rabbitvcs-0.13.3-1.el5-root
@@ -59,11 +60,11 @@ You'll see a lot of output; if the process completes successfully, you'll see th
+ /bin/rm -rf /tmp/rpmbuild/rabbitvcs-0.13.3-1.el5-root
+ exit 0
-As you can see, the successful conclusion of this process has dumped a new SRPM and several binary RPMs into the appropriate places in my build tree. At this point, you're all set; just install the newly built RPM.
+As you can see, the successful conclusion of this process has dumped a new SRPM and several binary RPMs into the appropriate places in my build tree. At this point, you are all set; just install the newly built RPM.
### Rebuilding from a specfile ###
-If there's no SRPM available, you'll need to find the specfile for the package. To do this, browse the RepoForge repository, e.g.
+If there is no SRPM available, you will need to find the specfile for the package. To do this, browse the RepoForge repository, e.g.
https://github.com/repoforge/rpms/blob/master/specs/<package name>/

0 comments on commit a1cb5bf

Please sign in to comment.