[Pkg-ruby-extras-maintainers] r748 - in website/src: .
ruby-pkg-tools
Lucas Nussbaum
lucas-guest at costa.debian.org
Tue Aug 8 08:35:29 UTC 2006
Author: lucas-guest
Date: 2006-08-08 08:35:27 +0000 (Tue, 08 Aug 2006)
New Revision: 748
Added:
website/src/30.subversion.en.page
website/src/ruby-pkg-tools/50.sources.en.page
Removed:
website/src/20.create.en.page
website/src/30.svn-build.en.page
website/src/ruby-pkg-tools/10.sources.en.page
Modified:
website/src/00.index.en.page
website/src/10.join.en.page
website/src/35.policy.en.page
website/src/50.upstream-devs.en.page
website/src/ruby-pkg-tools/00.index.en.page
website/src/ruby-pkg-tools/20.team-members.en.page
website/src/ruby-pkg-tools/30.cdbs.en.page
website/src/ruby-pkg-tools/40.uploaders.en.page
Log:
Many changes to the website, all described in a separate mail to the mailing list.
Modified: website/src/00.index.en.page
===================================================================
--- website/src/00.index.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/00.index.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -5,24 +5,19 @@
---
h2. Welcome to the Debian/Ruby Extras Site
-We're currently busy setting up this site, our Subversion infrastructure
-and tools. This page will be updated regularly, so please keep visiting.
-
-For more information about this project see the Alioth
-"project page":https://alioth.debian.org/projects/pkg-ruby-extras/ and the
-"mailinglist":http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers/.
-For general Debian/Ruby information the main
-"Debian Ruby list":http://lists.debian.org/debian-ruby/.
-
-h2. About Us
-
The Debian/Ruby Extras team currently has two goals:
-# Creating and maintaining a @libruby-extras@ package that bundles small
- but useful libraries that could have been in stdlib but aren't.
-# Make a team effort of packaging a lot of useful Ruby libraries (not all
+# Creating and maintaining a *@libruby-extras@ package that bundles small
+ but useful libraries* that could have been in stdlib but aren't.
+# Make a *team effort of packaging a lot of useful Ruby libraries* (not all
necessarily part of @libruby-extras@) and applications to improve
quality and maintenance.
+For more information about this project, see the Alioth
+"project page":https://alioth.debian.org/projects/pkg-ruby-extras/ and the
+"mailing list":http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers/.
+For general Debian/Ruby information, see the main
+"Debian Ruby mailing list":http://lists.debian.org/debian-ruby/.
+
h2. News
h3. 2006.07.03 - @ruby-pkg-tools@ 0.10, more new members
@@ -79,7 +74,7 @@
h3. 2005.09.27 - Adding @libxml-ruby@ and @libxslt-ruby@
Due to a recent "request for adoption":http://lists.debian.org/debian-devel/2005/09/msg00854.html on libxml-ruby and libxslt-ruby, I
-have decided to adopt both libraries and bring it to pkg-ruby-extras.
+have decided to adopt both libraries and bring it to pkg-ruby-extras
This will, hopefully, speed up a bit the presence of a second source
package by the team, following the previous @ruby-pkg-tools@ package
already in the archive. _(damog)_
Modified: website/src/10.join.en.page
===================================================================
--- website/src/10.join.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/10.join.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -8,15 +8,17 @@
follow the following guidelines.
* Contact us first on our
- "mailinglist":http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers/.
+ "mailing list":http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers/.
* Make sure that you have an
"Alioth":http://alioth.debian.org/account/register.php account, so that
we can give you access/permissions.
* Have a look at our Alioth "project
page":http://alioth.debian.org/projects/pkg-ruby-extras/.
-* When given access, add yourself to the @pkg-ruby-extras.team@ file (see
+* When given access (there's a delay before getting your account on
+ svn.debian.org, see the
+ "Alioth FAQ":http://wiki.debian.org/AliothFAQ for details), add yourself
+ to the @pkg-ruby-extras.team@ file (see
also "this page":ruby-pkg-tools/team-members.html), bump the minor
version, upload this version and tag it afterwards. Please do not forget
to add a comma at the end of the previous line, as this would break
generated control files.
-
Deleted: website/src/20.create.en.page
===================================================================
--- website/src/20.create.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/20.create.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -1,74 +0,0 @@
----
-title: Creating a Package
-inMenu: true
----
-h2. How to Create a Debian/Ruby Package?
-
-_This page still has to be finished..._
-
-h3. Preparing the source
-
-...
-
-h3. Using CDBS
-
-First of all, the CDBS classes that are available can only be used for for
-libraries or applications that use @setup.rb@ (or @install.rb@) or
- at extconf.rb@. If the library you want to package doesn't use @setup.rb@ or
- at extconf.rb@ you'll have to either (1) add it yourself and make sure it
-works as expected, or (2) simply not use the class and package manually.
-
-If you want to use the CDBS classes, you have to build-depend on
- at ruby-pkg-tools@. Then, in your @debian/rules@, you'll have to include it,
-and @uploaders.mk@ if you are in the Ruby Extras maintainers team. If you
-also include @debhelper.mk@, your rules will resemble this example:
-
-<pre><code>#!/usr/bin/make -f
-
-include /usr/share/cdbs/1/rules/debhelper.mk
-include /usr/share/ruby-pkg-tools/1/class/ruby-setup-rb.mk
-include /usr/share/ruby-pkg-tools/1/rules/uploaders.mk
-</code></pre>
-
-
-There are a number of configuration variables you can set. For more
-information, see the "CDBS class information page":ruby-pkg-tools/cdbs.html.
-
-h3. Using debhelper directly
-
-h3. Adding the package to the Subversion repository
-
-First, you have to build your package outside of the SVN tree. You should
-get something like that:
-<pre><code>.
-|-- libfeedparser-ruby-0.1/ (build dir)
-|-- libfeedparser-ruby1.8-dev_0.1-1_all.deb
-|-- libfeedparser-ruby1.8_0.1-1_all.deb
-|-- libfeedparser-ruby_0.1-1.diff.gz
-|-- libfeedparser-ruby_0.1-1.dsc
-|-- libfeedparser-ruby_0.1-1_i386.changes
-|-- libfeedparser-ruby_0.1.orig.tar.gz
-`-- libxfeedparser-ruby_0.1-1_all.deb
-</code></pre>
-
-Then just do:
-<pre><code>svn-inject -v -o libfeedparser-ruby_0.1-1.dsc \
- svn+ssh://LOGIN@svn.debian.org/svn/pkg-ruby-extras/packages/</code></pre>
-
-You should not try to import your package manually: this handles a lot of small gory details you do not want to know.
-
-*N.B.* Make sure that you have registered a SSH key, else you will be
-prompted for your password a good dozen of times.
-
-This script creates a @branches@ directory in svn that we do not use. You should remove this directory after the svn-inject operation. Get first a fresh copy of the package you just injected in svn, then delete the unneeded @branches@ directory.
-<pre><code>$ cd Debian/packages
-$ svn co svn+ssh://svn.debian.org/svn/pkg-ruby-extras/packages/libfoo-ruby
-[...]
-$ cd libfoo-ruby
-$ svn remove branches
-[...]
-$ svn commit -m "Deleted branches directory."
-</pre></code>
-
-Finally, it's a good idea to add the upstream source in the @pkg-ruby-extras.sources@ file. See "Upstream Sources":ruby-pkg-tools/sources.html.
-
Copied: website/src/30.subversion.en.page (from rev 747, website/src/30.svn-build.en.page)
===================================================================
--- website/src/30.svn-build.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/30.subversion.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -0,0 +1,111 @@
+---
+title: Using Subversion
+inMenu: true
+---
+h2. Using the Subversion repository
+
+Follow the instructions for building the @pkg-ruby-extras@ packages.
+
+If you need general help with Subversion, an
+"online book":http://svnbook.red-bean.com/ is available.
+
+h3. Repository structure
+
+Our repository is structured like this:
+
+<pre><code>pkg-ruby-extras
++-- packages
+ +-- libfoo-ruby
+ +-- libbar-ruby
+ +-- ...
++-- tools
+ +-- ...
++-- website
+ +-- ...</code></pre>
+
+All our packages will live inside @packages/@ directory. Each package directory
+will have a structure common to subversion-managed projects:
+
+<pre><code>libfoo-ruby
++-- branches
++-- tags
++-- trunk</code></pre>
+
+ at trunk@ is where your current version lives. @tags@ is where you copy snapshots
+when uploading. So there must be one tagged copy for each uploaded version of a
+package. @branches@ is were you can make copies to experiment something new without
+breaking the @trunk at . Those are common-used conventions: you can look with more
+details in the "SVN Book":http://svnbook.red-bean.com/.
+
+h3. Injecting a new package to Subversion
+
+First, you have to build your package outside of the SVN tree. You should
+get something like that:
+<pre><code>.
+|-- libfeedparser-ruby-0.1/ (build dir)
+|-- libfeedparser-ruby1.8-dev_0.1-1_all.deb
+|-- libfeedparser-ruby1.8_0.1-1_all.deb
+|-- libfeedparser-ruby_0.1-1.diff.gz
+|-- libfeedparser-ruby_0.1-1.dsc
+|-- libfeedparser-ruby_0.1-1_i386.changes
+|-- libfeedparser-ruby_0.1.orig.tar.gz
+`-- libxfeedparser-ruby_0.1-1_all.deb
+</code></pre>
+
+Then just do:
+<pre><code>svn-inject -v -o libfeedparser-ruby_0.1-1.dsc \
+ svn+ssh://LOGIN@svn.debian.org/svn/pkg-ruby-extras/packages/</code></pre>
+
+You should not try to import your package manually: this handles a lot of small gory details you do not want to know.
+
+*N.B.* Make sure that you have registered a SSH key, else you will be
+prompted for your password a good dozen of times.
+
+This script creates a @branches@ directory in svn that we do not use. You should remove this directory after the svn-inject operation. Get first a fresh copy of the package you just injected in svn, then delete the unneeded @branches@ directory.
+<pre><code>$ cd Debian/packages
+$ svn co svn+ssh://svn.debian.org/svn/pkg-ruby-extras/packages/libfoo-ruby
+[...]
+$ cd libfoo-ruby
+$ svn remove branches
+[...]
+$ svn commit -m "Deleted branches directory."
+</pre></code>
+
+h3. Checking out
+
+You can check a package out by using:
+
+<pre><code>$ svn checkout svn+ssh://svn.debian.org/svn/pkg-ruby-extras/packages/libfoo-ruby</code></pre>
+
+Alternatively, you can check out only the package's current version:
+<pre><code>$ svn checkout svn+ssh://svn.debian.org/svn/pkg-ruby-extras/packages/libfoo-ruby/trunk</code></pre>
+
+Or the whole repository:
+<pre><code>$ svn checkout svn+ssh://svn.debian.org/svn/pkg-ruby-extras</code></pre>
+
+h3. Building with @svn-buildpackage@
+
+First, you must "download upstream sources":ruby-pkg-tools/sources.html.
+
+Then you have to change do the trunk directory:
+
+<code><pre>$ cd libfoo-ruby/trunk</pre></code>
+
+Inside @trunk/@, you can build the package with @svn-buildpackage@:
+
+<code><pre>$ svn-buildpackage -rfakeroot</pre></code>
+
+h3. Releasing and tagging
+
+After releasing the package, its current state must be tagged to keep the exact
+source used to build the uploaded package. This can be done from the package
+directory with (assuming the released version is @0.1-1@):
+
+<pre><code>$ svn copy trunk tags/0.1-1</code></pre>
+
+Alternatively, you can tell @svn-buildpackage@ to automatically tag the release
+after building using the option @--svn-tag at .
+
+*Attention:* use this option only when you are sure that this build will
+be the final build, just before upload.
+
Deleted: website/src/30.svn-build.en.page
===================================================================
--- website/src/30.svn-build.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/30.svn-build.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -1,74 +0,0 @@
----
-title: Using Subversion
-inMenu: true
----
-h2. Using the Subversion repository
-
-Follow the instructions for building the @pkg-ruby-extras@ packages.
-
-h3. Repository structure
-
-Our repository is structured like this:
-
-<pre><code>pkg-ruby-extras
-+-- packages
- +-- libfoo-ruby
- +-- libbar-ruby
- +-- ...
-+-- tools
- +-- ...
-+-- website
- +-- ...</code></pre>
-
-All our packages will live inside @packages/@ directory. Each package directory
-will have a structure common to subversion-managed projects:
-
-<pre><code>libfoo-ruby
-+-- branches
-+-- tags
-+-- trunk</code></pre>
-
- at trunk@ is where your current version lives. @tags@ is where you copy snapshots
-when uploading. So there must be one tagged copy for each uploaded version of a
-package. @branches@ is were you can make copies to experiment something new without
-breaking the @trunk at . Those are common-used conventions: you can look with more
-details in the "SVN Book":http://svnbook.red-bean.com/.
-
-h3. Checking out
-
-You can check a package out by using:
-
-<pre><code>$ svn checkout svn+ssh://svn.debian.org/svn/pkg-ruby-extras/packages/libfoo-ruby</code></pre>
-
-Alternatively, you can check out only the package's current version:
-<pre><code>$ svn checkout svn+ssh://svn.debian.org/svn/pkg-ruby-extras/packages/libfoo-ruby/trunk</code></pre>
-
-Or the whole repository:
-<pre><code>$ svn checkout svn+ssh://svn.debian.org/svn/pkg-ruby-extras</code></pre>
-
-h3. Building with @svn-buildpackage@
-
-First, you must "download upstream sources":ruby-pkg-tools/sources.html.
-
-Then you have to change do the trunk directory:
-
-<code><pre>$ cd libfoo-ruby/trunk</pre></code>
-
-Inside @trunk/@, you can build the package with @svn-buildpackage@:
-
-<code><pre>$ svn-buildpackage -rfakeroot</pre></code>
-
-h3. Releasing and tagging
-
-After releasing the package, its current state must be tagged to keep the exact
-source used to build the uploaded package. This can be done from the package
-directory with (assuming the released version is @0.1-1@):
-
-<pre><code>$ svn copy trunk tags/0.1-1</code></pre>
-
-Alternatively, you can tell @svn-buildpackage@ to automatically tag the release
-after building using the option @--svn-tag at .
-
-*Attention:* use this option only when you are sure that this build will
-be the final build, just before upload.
-
Modified: website/src/35.policy.en.page
===================================================================
--- website/src/35.policy.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/35.policy.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -1,10 +1,10 @@
---
title: Ruby Policy
-inMenu: false
+inMenu: true
---
h1. Debian Ruby Policy
-This document SHOULD NOT be considered policy yet. It is only a support
+*This document SHOULD NOT be considered a policy yet*. It is only a support
for discussion. Other documents worth reading:
* "Debian Ruby Policy":http://pkg-ruby.alioth.debian.org/ruby-policy.html/index.html:
a draft policy written by the pkg-ruby alioth team.
Modified: website/src/50.upstream-devs.en.page
===================================================================
--- website/src/50.upstream-devs.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/50.upstream-devs.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -1,6 +1,6 @@
---
-title: Upstream Developers
-inMenu: false
+title: Dear Upstream Developers
+inMenu: true
---
h2. Upstream Developers, Be Nice to Distributions (Re)Packagers!
Modified: website/src/ruby-pkg-tools/00.index.en.page
===================================================================
--- website/src/ruby-pkg-tools/00.index.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/ruby-pkg-tools/00.index.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -6,19 +6,21 @@
h2. Introduction
Most of the packaging work can be simplified using the Ruby Package Tools.
-The tools are contained in the @ruby-pkg-tools@ package, available from
-Sid. It contains the following:
+The tools are contained in the @ruby-pkg-tools@ package, available in Debian.
+It contains the following:
-* A file (@pkg-ruby-extras.sources@) which contains a list of upstream
- sources, which versions are where to get. The file is used by the
- @pkg-ruby-get-sources@ for locating and retrieving upstream sources for
- packages to be built that are checked out from the "Subversion
- repository":../svn-build.html.
-* A file (@pkg-ruby-extras.team@) containing the names and email addresses
+* A "file":team-members.html (@pkg-ruby-extras.team@) containing the names and email addresses
of all team members.
-* A CDBS class (@ruby-setup-rb.mk@) that is usable to create Debian packages
+* A "CDBS class":cdbs.html (@ruby-setup-rb.mk@) that is usable to create Debian packages
from Ruby upstream libraries and apps that use @setup.rb@ as their
installer.
-* A CDBS rule (@uploaders.mk@) to perform a substitution on build-time,
+* A "CDBS rule":uploaders.html (@uploaders.mk@) to perform a substitution on build-time,
filling in the Uploaders field with the team members.
* In the future: dh-make-ruby stuff to automatically Debianize a source tree.
+* A "file":sources.html (@pkg-ruby-extras.sources@) which contains a list of upstream
+ sources, which versions are where to get. The file is used by the
+ @pkg-ruby-get-sources@ for locating and retrieving upstream sources for
+ packages to be built that are checked out from the "Subversion
+ repository":../subversion.html. However, the preferred way to retrieve
+ upstream sources is by using a @debian/watch@ file. You should only add
+ your package to @pkg-ruby-extras.sources@ if you cannot use a watch file.
Deleted: website/src/ruby-pkg-tools/10.sources.en.page
===================================================================
--- website/src/ruby-pkg-tools/10.sources.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/ruby-pkg-tools/10.sources.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -1,59 +0,0 @@
----
-title: Upstream Sources
-inMenu: true
----
-h2. Retrieving Upstream Sources
-
-Since after much discussion it was decided _not_ to put all the upstream
-sources of every package into the Subversion repository, a tool was added
-to this package to help retrieving it. This tool, @pkg-ruby-get-sources@ is
-described below.
-
-h3. Basic usage
-
-A basic usage scenario for @pkg-ruby-get-sources@ is to do a checkout,
-get the upstream source and build:
-
- $ cd Debian/packages
- $ svn co svn+ssh://svn.debian.org/svn/pkg-ruby-extras/packages/libfoo-ruby
- [...]
- $ cd libfoo-ruby/trunk
- $ mkdir ../tarballs
- $ pkg-ruby-get-sources
- [100%] http://somesite/path/to/foo-ruby-0.1.tar.gz
- $ ls ../tarballs
- libfoo-ruby_0.1.orig.tar.gz
- $ svn-buildpackage [...]
-
-Note that @pkg-ruby-get-sources@ retrieves the tarball and takes care of
-the naming of the file locally so that it suits the Debian source package
-name. For example see above where @foo-ruby-0.1.tar.gz@ is automatically
-renamed to @libfoo-ruby_0.1.orig.tar.gz at .
-
-h3. Registering sources
-
-When there is a entirely new package or upstream release of a package, the
-source tarball must be registered. This can be done by editting the file
-that is used to locate the sources. Retrieve from Subversion:
-
- /svn/pkg-ruby-extras/tools/ruby-pkg-tools/trunk/pkg-ruby-extras.sources
-
-and edit it. This file follows the "YAML":http://yaml.org/ format.
-
-* For adding a new package @libfoo-ruby@ version 0.1, append:
-
- <pre><code>libfoo-ruby:
- "0.1": http://somesite/path/to/foo-ruby-0.1.tar.gz</pre></code>
-
-* For adding a new upstream version 0.2 for @libfoo-ruby@, append to the previous
- lines:
-
- <pre><code> "0.2": http://somesite/path/to/foo-ruby-0.2.tar.gz</code></pre>
-
-h3. Other features
-
- at pkg-ruby-get-sources@ allows for selecting different sources files
-(@--sources@) instead of using the one that comes with @ruby-pkg-tools@ by
-default, so you can use your own. It also can list all available sources
-(@--list-available@) or download to a different target directory
-(@--target-directory@).
Modified: website/src/ruby-pkg-tools/20.team-members.en.page
===================================================================
--- website/src/ruby-pkg-tools/20.team-members.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/ruby-pkg-tools/20.team-members.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -9,3 +9,5 @@
team, this file must be updated. Please refer to "this page":../join.html
for more information about updating this file. The list is mostly used by
the "uploaders rule":uploaders.html.
+
+*N.B:* Double check that you haven't forgotten a comma when adding yourself!
Modified: website/src/ruby-pkg-tools/30.cdbs.en.page
===================================================================
--- website/src/ruby-pkg-tools/30.cdbs.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/ruby-pkg-tools/30.cdbs.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -44,4 +44,5 @@
HOWTO":https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml.
*N.B.* When using either of these classes, don't forget to add
-"ruby-pkg-tools" to the Build-Depends(-Indep) field!
+* "debhelper" and "cdbs" to the Build-Depends field
+* "ruby-pkg-tools" to the Build-Depends(possibly Build-Depends-Indep) field
Modified: website/src/ruby-pkg-tools/40.uploaders.en.page
===================================================================
--- website/src/ruby-pkg-tools/40.uploaders.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/ruby-pkg-tools/40.uploaders.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -1,11 +1,11 @@
---
-title: The Uploader Rule
+title: The Uploaders Rule
inMenu: true
---
-h2. The Uploader Rule
+h2. The Uploaders Rule
Regardless whether the CDBS class is used or a plain old rules file, one
-can use the uploader rule, @uploader.mk@, to automatically inject the
+can use the uploaders rule, @uploaders.mk@, to automatically inject the
members of the team in the Uploaders-field of the control file. Copy
@debian/control@ to @debian/control.in@, and add the following to
@debian/control.in@:
Copied: website/src/ruby-pkg-tools/50.sources.en.page (from rev 747, website/src/ruby-pkg-tools/10.sources.en.page)
===================================================================
--- website/src/ruby-pkg-tools/10.sources.en.page 2006-08-05 10:56:50 UTC (rev 747)
+++ website/src/ruby-pkg-tools/50.sources.en.page 2006-08-08 08:35:27 UTC (rev 748)
@@ -0,0 +1,63 @@
+---
+title: Upstream Sources
+inMenu: true
+---
+h2. Retrieving Upstream Sources
+
+Since after much discussion it was decided _not_ to put all the upstream
+sources of every package into the Subversion repository, a tool was added
+to this package to help retrieving it. This tool, @pkg-ruby-get-sources@ is
+described below.
+
+h3. Basic usage
+
+A basic usage scenario for @pkg-ruby-get-sources@ is to do a checkout,
+get the upstream source and build:
+
+ $ cd Debian/packages
+ $ svn co svn+ssh://svn.debian.org/svn/pkg-ruby-extras/packages/libfoo-ruby
+ [...]
+ $ cd libfoo-ruby/trunk
+ $ mkdir ../tarballs
+ $ pkg-ruby-get-sources
+ [100%] http://somesite/path/to/foo-ruby-0.1.tar.gz
+ $ ls ../tarballs
+ libfoo-ruby_0.1.orig.tar.gz
+ $ svn-buildpackage [...]
+
+Note that @pkg-ruby-get-sources@ retrieves the tarball and takes care of
+the naming of the file locally so that it suits the Debian source package
+name. For example see above where @foo-ruby-0.1.tar.gz@ is automatically
+renamed to @libfoo-ruby_0.1.orig.tar.gz at .
+
+h3. Where does it find upstream sources?
+
+There are two ways to find the upstream sources:
+# Using the package's watch file. This is the preferred method.
+# Using the @pkg-ruby-extras.sources@ file, described below. This should only be used for packages where watch files are not a solution.
+
+h3. Registering sources using the @pkg-ruby-extras.sources@ file
+
+Retrieve from Subversion:
+
+ /svn/pkg-ruby-extras/tools/ruby-pkg-tools/trunk/pkg-ruby-extras.sources
+
+and edit it. This file follows the "YAML":http://yaml.org/ format.
+
+* For adding a new package @libfoo-ruby@ version 0.1, append:
+
+ <pre><code>libfoo-ruby:
+ "0.1": http://somesite/path/to/foo-ruby-0.1.tar.gz</pre></code>
+
+* For adding a new upstream version 0.2 for @libfoo-ruby@, append to the previous
+ lines:
+
+ <pre><code> "0.2": http://somesite/path/to/foo-ruby-0.2.tar.gz</code></pre>
+
+h3. Other features
+
+ at pkg-ruby-get-sources@ allows for selecting different sources files
+(@--sources@) instead of using the one that comes with @ruby-pkg-tools@ by
+default, so you can use your own. It also can list all available sources
+(@--list-available@) or download to a different target directory
+(@--target-directory@).
More information about the pkg-ruby-extras-maintainers
mailing list