[DRE-commits] r3506 - in website/src: . ruby-pkg-tools
Paul van Tilburg
paulvt at alioth.debian.org
Tue May 5 11:16:17 UTC 2009
Author: paulvt
Date: 2009-05-05 11:16:17 +0000 (Tue, 05 May 2009)
New Revision: 3506
Modified:
website/src/00.index.en.page
website/src/00.index.es.page
website/src/00.index.nl.page
website/src/10.join.en.page
website/src/30.subversion.en.page
website/src/35.policy.en.page
website/src/40.rubygems.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
website/src/ruby-pkg-tools/50.sources.en.page
Log:
Updated the website by removing all hardlinks, now differently interpreted by RedCloth.
Modified: website/src/00.index.en.page
===================================================================
--- website/src/00.index.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/00.index.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -6,156 +6,77 @@
h2. Welcome to the Debian/Ruby Extras Site
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
- necessarily part of @libruby-extras@) and applications to improve
- quality and maintenance.
+# 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/.
+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. 2009.02.14 - Lenny released!
-Debian GNU/Linux "Lenny" 5.0 has just been released. This will mark the
-point that we restart pushing new upstream to unstable. Also, a discussion
-was started to deal with the transition to Ruby 1.9 and/or better
-multi-interpreter support.
+Debian GNU/Linux "Lenny" 5.0 has just been released. This will mark the point that we restart pushing new upstream to unstable. Also, a discussion was started to deal with the transition to Ruby 1.9 and/or better multi-interpreter support.
-Since the last news message (quite a while ago), we have welcomed to our
-team: Roberto Sanchez, Michael Schutte and Ryan Niebur.
+Since the last news message (quite a while ago), we have welcomed to our team: Roberto Sanchez, Michael Schutte and Ryan Niebur. _(paulvt)_
h3. 2008.04.08 - QA Report
-We have set up the "Debian
-QA":http://wiki.debian.org/Teams/DebianPerlGroup/DebianQA report page,
-developed by the "Debian Perl Group":http://pkg-perl.alioth.debian.org/,
-to keep track of the status of our packages in the archive, in SVN, in NEW,
-upstream, etc. You can see our QA report
-"here":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/qareport.cgi.
+We have set up the "Debian QA":http://wiki.debian.org/Teams/DebianPerlGroup/DebianQA report page, developed by the "Debian Perl Group":http://pkg-perl.alioth.debian.org/, to keep track of the status of our packages in the archive, in SVN, in NEW, upstream, etc. You can see our QA report "here":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/qareport.cgi.
-We also welcomed three new members to our team, namely: Maxim Komar, Stig
-Sandbeck Mathisen, and Leandro Nunes dos Santos. Welcome!
+We also welcomed three new members to our team, namely: Maxim Komar, Stig Sandbeck Mathisen, and Leandro Nunes dos Santos. Welcome! _(paulvt)_
h3. 2007.10.06 - Meeting minutes
-A few weeks after the actual Debian/Ruby Extras meeting
-took place on Debconf 7, the minutes have become
-"available":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2007-October/001705.html
-containing many future action points for the team. _paulvt_
+A few weeks after the actual Debian/Ruby Extras meeting took place on Debconf 7, the minutes have become "available":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2007-October/001705.html containing many future action points for the team. _(paulvt)_
h3. 2007.01.02 - A new year
The team wishes everyone a happy and good new year!
-With the primary goals reached the team will focus on the next release,
-Lenny. It will encompass Ruby policy changes, so more consistancey, more
-libraries and applications under team maintenance. Just before the new
-year started, the team received two new team members: Florian Ragwitz and
-Gunnar Wolf. Welcome! _paulvt_
+With the primary goals reached the team will focus on the next release, Lenny. It will encompass Ruby policy changes, so more consistancey, more libraries and applications under team maintenance. Just before the new year started, the team received two new team members: Florian Ragwitz and Gunnar Wolf. Welcome! _(paulvt)_
h3. 2006.11.20 - Goals reached!
-As of yesterday Debian Sid (and hopefully soon Etch too) contains the
- at libruby-extras@ meta-package. Also I can say that a lot of Ruby libraries
-and applications, 42 at the moment and counting, are now maintained
-succesfully by the team. I am proud that we were able to meet both goals
-in just over a year and hope we can continue pursuing improvements in
-quality and consistency in the future. _paulvt_
+As of yesterday Debian Sid (and hopefully soon Etch too) contains the @libruby-extras@ meta-package. Also I can say that a lot of Ruby libraries and applications, 42 at the moment and counting, are now maintained succesfully by the team. I am proud that we were able to meet both goals in just over a year and hope we can continue pursuing improvements in quality and consistency in the future. _(paulvt)_
h3. 2006.11.09 - Meta-package created, new members
-Because the freeze before the Etch is near, the team has been working to
-finish some of "the todo
-items":http://paul.luon.net/journal/debian/DebianRubyExtrasEtchToDo that I
-have set for myself for the Etch release. A lot of work-in-progress
-packages have been uploaded and some initial version of the
- at libruby-extras@ package has been created and will be uploaded to Sid soon.
+Because the freeze before the Etch is near, the team has been working to finish some of "the todo items":http://paul.luon.net/journal/debian/DebianRubyExtrasEtchToDo that I have set for myself for the Etch release. A lot of work-in-progress packages have been uploaded and some initial version of the @libruby-extras@ package has been created and will be uploaded to Sid soon.
-Meanwhile, Patrick Ringl has joined the team to work on @libinline-ruby@
-and @ruby-yarv@, a prospective version of Ruby. Filipe Lautert also has
-joined the team very recently and took on the maintenance of @libxml-ruby@
-and @libxslt-ruby@ which have been in an orphaned state for quite some time
-now. Welcome to the team! _paulvt_
+Meanwhile, Patrick Ringl has joined the team to work on @libinline-ruby@ and @ruby-yarv@, a prospective version of Ruby. Filipe Lautert also has joined the team very recently and took on the maintenance of @libxml-ruby@ and @libxslt-ruby@ which have been in an orphaned state for quite some time now. Welcome to the team! _(paulvt)_
h3. 2006.07.03 - @ruby-pkg-tools@ 0.10, more new members
-Yet more new members have joined our team: Rudi Cilibrasi, Vincent
-Fourmond and Sjoerd Simons. For now, Sjoerd will work solely on
-"Ruby/GStreamer0.10":https://trac.luon.net/ruby-gstreamer0.10/, while
-Vincent will bring us "Tioga":http://www.kitp.ucsb.edu/~paxton/tioga.html,
-"SciYAG":http://rubyforge.org/projects/sciyag/ and
-"mkmf2":http://mkmf2.rubyforge.org/ and Rudi will work on "Ruby
-SVM":http://rubysvm.cilibrar.com/ and
-"Complearn":http://complearn.cilibrar.com/.
+Yet more new members have joined our team: Rudi Cilibrasi, Vincent Fourmond and Sjoerd Simons. For now, Sjoerd will work solely on "Ruby/GStreamer0.10":https://trac.luon.net/ruby-gstreamer0.10/, while Vincent will bring us "Tioga":http://www.kitp.ucsb.edu/~paxton/tioga.html, "SciYAG":http://rubyforge.org/projects/sciyag/ and "mkmf2":http://mkmf2.rubyforge.org/ and Rudi will work on "Ruby SVM":http://rubysvm.cilibrar.com/ and "Complearn":http://complearn.cilibrar.com/.
-A week ago @ruby-pkg-tools@ 0.10 has been uploaded which fixes several
-small issues. With this upload support of the "upstream sources" file has
-been dropped and upstream sources should be retrieved via the
- at debian/watch@ files (required to be) included in all packages. _paulvt_
+A week ago @ruby-pkg-tools@ 0.10 has been uploaded which fixes several small issues. With this upload support of the "upstream sources" file has been dropped and upstream sources should be retrieved via the @debian/watch@ files (required to be) included in all packages. _(paulvt)_
h3. 2006.03.22 - @ruby-pkg-tools@ 0.8, new member
-A new version of the Ruby Package Tools has been uploaded today. This
-upload will cause some changes in the way of packaging and usage of the
-tools. Read more about it in this
-"email":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2006-March/000512.html.
+A new version of the Ruby Package Tools has been uploaded today. This upload will cause some changes in the way of packaging and usage of the tools. Read more about it in this "email":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2006-March/000512.html.
-Next to this upload has Ari Pollak joined our team and added
-"rcov":http://www.eigenclass.org/hiki.rb?cmd=view&p=rcov to our list of
-packaged tools and libraries. Other new packages that have been added in
-the past three months are:
-"libgpgme-ruby":http://packages.debian.org/unstable/libs/libgpgme-ruby,
-"librmagick-ruby":http://packages.debian.org/unstable/interpreters/librmagick-ruby,
-"liblog4r-ruby":http://packages.debian.org/unstable/devel/liblog4r-ruby,
-"libgnuplot-ruby":http://packages.debian.org/unstable/libs/libgnuplot-ruby,
-"feed2imap":http://packages.debian.org/unstable/net/feed2imap,
-"libjson-ruby":http://packages.debian.org/unstable/interpreters/libjson-ruby, and
-"libcairo-ruby":http://packages.debian.org/unstable/libs/libcairo-ruby.
-_paulvt_
+Next to this upload has Ari Pollak joined our team and added "rcov":http://www.eigenclass.org/hiki.rb?cmd=view&p=rcov to our list of packaged tools and libraries. Other new packages that have been added in the past three months are: "libgpgme-ruby":http://packages.debian.org/unstable/libs/libgpgme-ruby, "librmagick-ruby":http://packages.debian.org/unstable/interpreters/librmagick-ruby, "liblog4r-ruby":http://packages.debian.org/unstable/devel/liblog4r-ruby, "libgnuplot-ruby":http://packages.debian.org/unstable/libs/libgnuplot-ruby, "feed2imap":http://packages.debian.org/unstable/net/feed2imap, "libjson-ruby":http://packages.debian.org/unstable/interpreters/libjson-ruby, and "libcairo-ruby":http://packages.debian.org/unstable/libs/libcairo-ruby. _(paulvt)_
h3. 2006.01.01 - New member, @dh_rdoc@
-A new member has been added to our team: Thierry Reding. Welcome!
-Meanwhile, Esteban Manchado Velázquez started working on the development
-of "@dh_rdoc@":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wiki/index.cgi?DocumentationGeneration. _paulvt_
+A new member has been added to our team: Thierry Reding. Welcome! Meanwhile, Esteban Manchado Velázquez started working on the development of "@dh_rdoc@":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wiki/index.cgi?DocumentationGeneration. _(paulvt)_
h3. 2005.11.02 - New team members
-Recently a lot of people have joined "our team":https://alioth.debian.org/project/memberlist.php?group_id=30665.
-The following Debian-developers-to-be are reinforcing us: Daigo Moriwaki,
-Lucas Nussbaum and Arnaud Cornet. We hope that as a team we can make a
-difference soon in the area of Ruby library and application packaging.
-Stay tuned... _paulvt_
+Recently a lot of people have joined "our team":https://alioth.debian.org/project/memberlist.php?group_id=30665. The following Debian-developers-to-be are reinforcing us: Daigo Moriwaki, Lucas Nussbaum and Arnaud Cornet. We hope that as a team we can make a difference soon in the area of Ruby library and application packaging. Stay tuned... _(paulvt)_
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
-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_
+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 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)_
h3. 2005.09.03 - Integrated Wiki
-I have added "Kwiki":http://www.kwiki.org/ to the webpage setup and it is
-"integrated":/cgi-bin/wiki/index.cgi in this page through page specific
-WikiLinks. _paulvt_
+I have added "Kwiki":http://www.kwiki.org/ to the webpage setup and it is "integrated":/cgi-bin/wiki/index.cgi in this page through page specific WikiLinks. _(paulvt)_
h3. 2005.09.01 - @ruby-pkg-tools@ accepted in the archive
-The @ruby-pkg-tools@ package (version 0.1) got accepted and thus through
-the _new_ queue yesterday night. This means that @ruby-pkg-tools@ will be
-available in sid this evening and Ruby packages can start to "use
-it":ruby-pkg-tools/index.html. _paulvt_
+The @ruby-pkg-tools@ package (version 0.1) got accepted and thus through the _new_ queue yesterday night. This means that @ruby-pkg-tools@ will be available in sid this evening and Ruby packages can start to "use it":ruby-pkg-tools/index.html. _(paulvt)_
h3. 2005.08.29 - First website attempt
-I've put online a first version of the website of the Debian/Ruby Extras
-team. The source files will soon arrive in Subversion, so that everyone
-can adapt and add stuff. _paulvt_
+I've put online a first version of the website of the Debian/Ruby Extras team. The source files will soon arrive in Subversion, so that everyone can adapt and add stuff. _(paulvt)_
Modified: website/src/00.index.es.page
===================================================================
--- website/src/00.index.es.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/00.index.es.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -5,83 +5,44 @@
---
h2. Bienvenido a la Página del Proyecto Debian/Ruby Extras
-Actualmente estamos ocupados poniendo a punto esta página, nuestra
-infraestructura para Subversion y nuestras herramientas. Esta página se
-actualizará con regularidad, así que siga visitándola.
+Actualmente estamos ocupados poniendo a punto esta página, nuestra infraestructura para Subversion y nuestras herramientas. Esta página se actualizará con regularidad, así que siga visitándola.
-Para más información sobre este proyecto vea la "página del
-proyecto":https://alioth.debian.org/projects/pkg-ruby-extras/ y las "listas de
-correo":http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers/
-en Alioth. Hay información más general sobre Ruby en Debian en la "lista de Ruby en Debian":http://lists.debian.org/debian-ruby/.
+Para más información sobre este proyecto vea la "página del proyecto":https://alioth.debian.org/projects/pkg-ruby-extras/ y las "listas de correo":http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers/ en Alioth. Hay información más general sobre Ruby en Debian en la "lista de Ruby en Debian":http://lists.debian.org/debian-ruby/.
h2. Sobre Nosotros
El equipo de Debian/Ruby Extras tiene dos objetivos:
-# Crear y mantener un paquete @libruby-extras@ que contenga pequeños pero
- útiles módulos que podrían venir de serie con Ruby, pero que no vienen.
-# Crear un equipo para empaquetar módulos útiles de Ruby (no necesariamente
- todos parte de @libruby-extras@) y aplicaciones, manteniendo un alto nivel de
- calidad.
+# Crear y mantener un paquete @libruby-extras@ que contenga pequeños pero útiles módulos que podrían venir de serie con Ruby, pero que no vienen.
+# Crear un equipo para empaquetar módulos útiles de Ruby (no necesariamente todos parte de @libruby-extras@) y aplicaciones, manteniendo un alto nivel de calidad.
h2. Noticias
h3. 22/03/2006 - @ruby-pkg-tools@ 0.8, nuevo miembro
-Hoy hemos subido una nueva versión de las herramientas de empaquetamiento para
-Ruby. Esta nueva versión provocará algunos cambios en la forma de empaquetar
-y en la forma de usar las herramientas. Puedes leer más sobre esto en "este
-hilo":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2006-March/000512.html.
+Hoy hemos subido una nueva versión de las herramientas de empaquetamiento para Ruby. Esta nueva versión provocará algunos cambios en la forma de empaquetar y en la forma de usar las herramientas. Puedes leer más sobre esto en "este hilo":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2006-March/000512.html.
-Poco después de subir la nueva versión, Ari Pollak se unió a nuestro equipo
-y añadió "rcov":http://www.eigenclass.org/hiki.rb?cmd=view&p=rcov a nuestra
-lista de herramientas y módulos empaquetados. Otros paquetes que se han
-añadido en los últimos tres meses son:
-"libgpgme-ruby":http://packages.debian.org/unstable/libs/libgpgme-ruby,
-"librmagick-ruby":http://packages.debian.org/unstable/interpreters/librmagick-ruby,
-"liblog4r-ruby":http://packages.debian.org/unstable/devel/liblog4r-ruby,
-"libgnuplot-ruby":http://packages.debian.org/unstable/libs/libgnuplot-ruby,
-"feed2imap":http://packages.debian.org/unstable/net/feed2imap,
-"libjson-ruby":http://packages.debian.org/unstable/interpreters/libjson-ruby, and
-"libcairo-ruby":http://packages.debian.org/unstable/libs/libcairo-ruby.
-_(paulvt)_
+Poco después de subir la nueva versión, Ari Pollak se unió a nuestro equipo y añadió "rcov":http://www.eigenclass.org/hiki.rb?cmd=view&p=rcov a nuestra lista de herramientas y módulos empaquetados. Otros paquetes que se han añadido en los últimos tres meses son: "libgpgme-ruby":http://packages.debian.org/unstable/libs/libgpgme-ruby, "librmagick-ruby":http://packages.debian.org/unstable/interpreters/librmagick-ruby, "liblog4r-ruby":http://packages.debian.org/unstable/devel/liblog4r-ruby, "libgnuplot-ruby":http://packages.debian.org/unstable/libs/libgnuplot-ruby, "feed2imap":http://packages.debian.org/unstable/net/feed2imap, "libjson-ruby":http://packages.debian.org/unstable/interpreters/libjson-ruby, and "libcairo-ruby":http://packages.debian.org/unstable/libs/libcairo-ruby. _(paulvt)_
h3. 01/01/2006 - Nuevo miembro, @dh_rdoc@
-Tenemos un nuevo miembro en el equipo: Thierry Reding. ¡Bienvenido!
-Mientras tanto, Esteban Manchado Velázquez ha empezado a trabajar en el desarrollo de "@dh_rdoc@":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wiki/index.cgi?DocumentationGeneration. _(paulvt)_
-
+Tenemos un nuevo miembro en el equipo: Thierry Reding. ¡Bienvenido! Mientras tanto, Esteban Manchado Velázquez ha empezado a trabajar en el desarrollo de "@dh_rdoc@":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wiki/index.cgi?DocumentationGeneration. _(paulvt)_
h3. 02/11/2005 - Nuevos miembros
-Últimamente hemos tenido muchas incorporaciones al
-"equipo":https://alioth.debian.org/project/memberlist.php?group_id=30665. Los
-siguientes candidatos a desarrollador de Debian vienen a reforzarlo: Daigo
-Moriwaki, Lucas Nussbaum y Arnaud Cornet. Esperamos poder ser útiles en el área
-de empaquetamiento de módulos y aplicaciones de Ruby. Permanezcan atentos...
-_(paulvt)_
+Últimamente hemos tenido muchas incorporaciones al "equipo":https://alioth.debian.org/project/memberlist.php?group_id=30665. Los siguientes candidatos a desarrollador de Debian vienen a reforzarlo: Daigo Moriwaki, Lucas Nussbaum y Arnaud Cornet. Esperamos poder ser útiles en el área de empaquetamiento de módulos y aplicaciones de Ruby. Permanezcan atentos... _(paulvt)_
h3. 27/09/2005 - Añadidos @libxml-ruby@ y @libxslt-ruby@
-Debido a un reciente "request for
-adoption":http://lists.debian.org/debian-devel/2005/09/msg00854.html sobre
-libxml-ruby y libxslt-ruby, decidí adoptar ambos módulos y añadirlos a
- at pkg-ruby-extras@. Esto, espero, acelerará un poco la presencia de un segundo
-paquete fuente del equipo, después del anterior @ruby-pkg-tools@, ya en el archivo de Debian. _(damog)_
+Debido a un reciente "request for adoption":http://lists.debian.org/debian-devel/2005/09/msg00854.html sobre libxml-ruby y libxslt-ruby, decidí adoptar ambos módulos y añadirlos a @pkg-ruby-extras at . Esto, espero, acelerará un poco la presencia de un segundo paquete fuente del equipo, después del anterior @ruby-pkg-tools@, ya en el archivo de Debian. _(damog)_
h3. 03/09/2005 - Wiki integrado
-He añadido un "Kwiki":http://www.kwiki.org/ a la página, y además está
-"integrado":/cgi-bin/wiki/index.cgi mediante WikiLinks específicos a cada
-página. _(paulvt)_
+He añadido un "Kwiki":http://www.kwiki.org/ a la página, y además está "integrado":/cgi-bin/wiki/index.cgi mediante WikiLinks específicos a cada página. _(paulvt)_
h3. 01/09/2005 - @ruby-pkg-tools@ aceptado en el archivo
-El paquete @ruby-pkg-tools@ (versión 0.1) se ha aceptado, y por lo tanto entró
-en la cola _new_ ayer por la noche. Esto significa que @ruby-pkg-tools@ estará
-disponible en sid esta noche, y que los paquetes de Ruby pueden empezar a "usarlo":ruby-pkg-tools/index.html. _(paulvt)_
+El paquete @ruby-pkg-tools@ (versión 0.1) se ha aceptado, y por lo tanto entró en la cola _new_ ayer por la noche. Esto significa que @ruby-pkg-tools@ estará disponible en sid esta noche, y que los paquetes de Ruby pueden empezar a "usarlo":ruby-pkg-tools/index.html. _(paulvt)_
h3. 29/08/2005 - Primera prueba de página
-Acabo de poner disponible la primera versión de la página del equipo de
-Debian/Ruby Extras. Los fuentes llegarán pronto al Subversion, para que
-cualquiera pueda adaptarlo y añadir contenido. _(paulvt)_
+Acabo de poner disponible la primera versión de la página del equipo de Debian/Ruby Extras. Los fuentes llegarán pronto al Subversion, para que cualquiera pueda adaptarlo y añadir contenido. _(paulvt)_
Modified: website/src/00.index.nl.page
===================================================================
--- website/src/00.index.nl.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/00.index.nl.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -5,181 +5,87 @@
---
h2. Welkom op de Debian/Ruby Extra's Site
-Op dit moment zijn we nog bezig om deze site op te zetten, net als onze
-Subversion infrastructuur en gereedschappen. Deze pagina zal regelmatig
-geupdate worden, dus blijf hem bezoeken.
+Op dit moment zijn we nog bezig om deze site op te zetten, net als onze Subversion infrastructuur en gereedschappen. Deze pagina zal regelmatig geupdate worden, dus blijf hem bezoeken.
-Voor meer informatie over dit project, zie de
-"project pagina":https://alioth.debian.org/projects/pkg-ruby-extras/
-op Alioth en de
-"mailinglist":http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers/.
-Zie voor algemene informatie over Debian en Ruby de
-"Debian Ruby lijst":http://lists.debian.org/debian-ruby/.
+Voor meer informatie over dit project, zie de "project pagina":https://alioth.debian.org/projects/pkg-ruby-extras/ op Alioth en de "mailinglist":http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers/. Zie voor algemene informatie over Debian en Ruby de "Debian Ruby lijst":http://lists.debian.org/debian-ruby/.
h2. Over het Team
Het Debian/Ruby Extra's team heeft op dit moment twee hoofddoelen:
-# Het creëren en onderhouden van het @libruby-extras@ pakket, dat
- kleine maar toch nuttige bibliotheken bundelt, die in de standaard
- bibliotheek hadden kunnen zitten.
-# Het in teamverband packagen en onderhouden van een hoop nuttige Ruby
- bibliotheken (niet noodzakelijk onderdeel van @libruby-extras@) en
- applicaties om daarmee de kwaliteit en onderhoud te vergroten.
+# Het creëren en onderhouden van het @libruby-extras@ pakket, dat kleine maar toch nuttige bibliotheken bundelt, die in de standaard bibliotheek hadden kunnen zitten.
+# Het in teamverband packagen en onderhouden van een hoop nuttige Ruby bibliotheken (niet noodzakelijk onderdeel van @libruby-extras@) en applicaties om daarmee de kwaliteit en onderhoud te vergroten.
h2. Nieuws
h3. 15-02-2009 - Lenny is gereed en uitgekomen!
-Debian GNU/Linux "Lenny" 5.0 is zojuist uitgekomen. Dit is het punt waarop
-we weer zullen beginnen met het uploaded van nieuwe upstream naar unstable.
-Inmiddels is er ook een discussie gestart die aankomende transitie naar
-Ruby 1.9 en/of multi-interpreter ondersteuning behandelt.
+Debian GNU/Linux "Lenny" 5.0 is zojuist uitgekomen. Dit is het punt waarop we weer zullen beginnen met het uploaded van nieuwe upstream naar unstable. Inmiddels is er ook een discussie gestart die aankomende transitie naar Ruby 1.9 en/of multi-interpreter ondersteuning behandelt.
-Sinds het vorige nieuws bericht (en dat is een tijd geleden) hebben we de
-volgende leden in ons team kunnen verwelkomen: Roberto Sanchez, Michael
-Schutte en Ryan Niebur.
+Sinds het vorige nieuws bericht (en dat is een tijd geleden) hebben we de volgende leden in ons team kunnen verwelkomen: Roberto Sanchez, Michael Schutte en Ryan Niebur. _(paulvt)_
h3. 08-04-2008 - QA rapport
-We hebben de "Debian
-QA":http://wiki.debian.org/Teams/DebianPerlGroup/DebianQA rapport
-webpagina, ontwikkeld door de "Debian Perl
-Groep":http://pkg-perl.alioth.debian.org/, opgezet om de status van onze
-paketten in het archief, in de NEW wachtrij, in SVN en upstream in de gaten
-te kunnen houden met behulp van dit overzicht. Je kan ons QA rapport
-"hier":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/qareport.cgi
-vinden.
+We hebben de "Debian QA":http://wiki.debian.org/Teams/DebianPerlGroup/DebianQA rapport webpagina, ontwikkeld door de "Debian Perl Groep":http://pkg-perl.alioth.debian.org/, opgezet om de status van onze paketten in het archief, in de NEW wachtrij, in SVN en upstream in de gaten te kunnen houden met behulp van dit overzicht. Je kan ons QA rapport "hier":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/qareport.cgi vinden.
-Tevens hebben we weer drie nieuwe leden bij ons team kunnen verwelkomen.
-Dit zijn: Maxim Komar, Stig Sandbeck Mathisen en Leandro Nunes dos
-Stantos. Welkom!
+Tevens hebben we weer drie nieuwe leden bij ons team kunnen verwelkomen. Dit zijn: Maxim Komar, Stig Sandbeck Mathisen en Leandro Nunes dos
+Stantos. Welkom! _(paulvt)_
h3. 06-10-2007 - Notulen vergadering
-Enkele weken nadat de daadwerkelijke Debian/Ruby Extras vergadering
-heeft plaatsgevonden, zijn de notulen
-"beschikbaar":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2007-October/001705.html
-geworden. De notulen bevatten vele toekomstige actiepunten voor het
-team. _paulvt_
+Enkele weken nadat de daadwerkelijke Debian/Ruby Extras vergadering heeft plaatsgevonden, zijn de notulen "beschikbaar":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2007-October/001705.html geworden. De notulen bevatten vele toekomstige actiepunten voor het team. _(paulvt)_
h3. 02-01-2007 - Een nieuw jaar
Het team wenst iedereen een goed en gelukkig nieuw jaar!
-Nu de primaire doelen van het team bereik zijn, zal het zich nu focussen op
-de volgende release, genaamd Lenny. Deze release zal Ruby beleid wijzingen
-inhouden, dus meer consistentie, en ook meer bibliotheken en applicaties
-die door het team beheerd worden. Vlak voordat het nieuwe jaar begon,
-heeft het team twee nieuwe leden gekregen: Florian Ragwitz en Gunnar Wolf.
-Welkom! _paulvt_
+Nu de primaire doelen van het team bereik zijn, zal het zich nu focussen op de volgende release, genaamd Lenny. Deze release zal Ruby beleid wijzingen inhouden, dus meer consistentie, en ook meer bibliotheken en applicaties die door het team beheerd worden. Vlak voordat het nieuwe jaar begon, heeft het team twee nieuwe leden gekregen: Florian Ragwitz en Gunnar Wolf. Welkom! _(paulvt)_
h3. 20-11-2006 - De doelen zijn bereikt!
-Sinds gisteren bevat Debian Sid (en hopelijk binnenkort ook Etch) het
- at libruby-extras@ meta-pakket. Tevens kan ik melden dat veel Ruby
-bibliotheken en applicaties, 42 op het moment en dit blijft toenemen,
-succesvol beheerd worden door het team. Ik ben er trots op dat we beide
-hoofddoelen van het team in net iets meer dan een jaar hebben kunnen halen
-en ik hoop dat we nu verder kunnen gaan met het verbeteren van de kwaliteit
-en consistentie. _paulvt_
+Sinds gisteren bevat Debian Sid (en hopelijk binnenkort ook Etch) het @libruby-extras@ meta-pakket. Tevens kan ik melden dat veel Ruby bibliotheken en applicaties, 42 op het moment en dit blijft toenemen, succesvol beheerd worden door het team. Ik ben er trots op dat we beide hoofddoelen van het team in net iets meer dan een jaar hebben kunnen halen en ik hoop dat we nu verder kunnen gaan met het verbeteren van de kwaliteit en consistentie. _(paulvt)_
h3. 09-11-2006 - Meta-pakket in aanmaak, nieuwe leden
Omdat de "freeze" van Etch nabij is, helpt het team met het afronden van
-meerdere
-"zaken":http://paul.luon.net/journal/debian/DebianRubyExtrasEtchToDo die ik
-mezelf voorgenomen had af te hebben voor de Etch release. Veel van de
-werk-in-uitvoering (WIP) paketten zijn afgemaakt en opgestuurd naar Sid en
-er is een begin gemaakt met het creeren van het @libruby-extras@ pakket.
-Ook deze zal binnenkort naar Sid gestuurd worden.
+meerdere "zaken":http://paul.luon.net/journal/debian/DebianRubyExtrasEtchToDo die ik mezelf voorgenomen had af te hebben voor de Etch release. Veel van de werk-in-uitvoering (WIP) paketten zijn afgemaakt en opgestuurd naar Sid en er is een begin gemaakt met het creeren van het @libruby-extras@ pakket. Ook deze zal binnenkort naar Sid gestuurd worden.
-Ondertussen is Patrick Ringl bij het team gekomen om aan @libinline-ruby@
-en @ruby-yarv@, een vooruitblik op de nieuwe Ruby versie, te werken. Ook
-Filipe Lautert is recentlijk bij het team gekomen en heeft het onderhoud
-van de paketten @libxml-ruby@ en @libxslt-ruby@ op zich genomen, die al een
-lange tijd de "wees" status hadden. Welkom bij het team! _(paulvt)_
+Ondertussen is Patrick Ringl bij het team gekomen om aan @libinline-ruby@ en @ruby-yarv@, een vooruitblik op de nieuwe Ruby versie, te werken. Ook Filipe Lautert is recentlijk bij het team gekomen en heeft het onderhoud van de paketten @libxml-ruby@ en @libxslt-ruby@ op zich genomen, die al een lange tijd de "wees" status hadden. Welkom bij het team! _(paulvt)_
h3. 03-07-2006 - @ruby-pkg-tools@ 0.10, meer nieuwe leden
-Nog meer leden hebben zich bij ons team gevoegd: Rudi Cilibrasi, Vincent
-Fourmond en Sjoerd Simons. Voor nu zal Sjoerd alleen werken aan
-"Ruby/GStreamer0.10":https://trac.luon.net/ruby-gstreamer0.10/. Vincent
-brengt ons binnenkort pakketten voor
-"Tioga":http://www.kitp.ucsb.edu/~paxton/tioga.html,
-"SciYAG":http://rubyforge.org/projects/sciyag/ en
-"mkmf2":http://mkmf2.rubyforge.org/. Rudi werkt nog aan zijn packages voor
-"Ruby SVM":http://rubysvm.cilibrar.com/ en
-"Complearn":http://complearn.cilibrar.com/.
+Nog meer leden hebben zich bij ons team gevoegd: Rudi Cilibrasi, Vincent Fourmond en Sjoerd Simons. Voor nu zal Sjoerd alleen werken aan "Ruby/GStreamer0.10":https://trac.luon.net/ruby-gstreamer0.10/. Vincent brengt ons binnenkort pakketten voor "Tioga":http://www.kitp.ucsb.edu/~paxton/tioga.html, "SciYAG":http://rubyforge.org/projects/sciyag/ en "mkmf2":http://mkmf2.rubyforge.org/. Rudi werkt nog aan zijn packages voor "Ruby SVM":http://rubysvm.cilibrar.com/ en "Complearn":http://complearn.cilibrar.com/.
-Vorige week is @ruby-pkg-tools@ 0.10 geupload dat kleine problemen oplost
-in de CDBS klassen. Met deze upload komt de ondersteuning van het
-"upstream sources" bestand te vervallen en hoort broncode voortaan puur via
- at debian/watch@ te vinden en op te halen te zijn. Hierdoor moeten alle
-packages dus dit @watch at -bestand hebben.
+Vorige week is @ruby-pkg-tools@ 0.10 geupload dat kleine problemen oplost in de CDBS klassen. Met deze upload komt de ondersteuning van het "upstream sources" bestand te vervallen en hoort broncode voortaan puur via @debian/watch@ te vinden en op te halen te zijn. Hierdoor moeten alle packages dus dit @watch at -bestand hebben.
h3. 22-03-2006 - @ruby-pkg-tools@ 0.8, nieuw lid
-Vandaag is er een nieuwe versie van de Ruby Package Tools geupload. Deze
-upload zal wat wijzigingen in de manier van pakket-beheer en het gebruik van het
-gereedschap tot het gevolg hebben. Lees meer hierover in deze
-"email":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2006-March/000512.html.
+Vandaag is er een nieuwe versie van de Ruby Package Tools geupload. Deze upload zal wat wijzigingen in de manier van pakket-beheer en het gebruik van het gereedschap tot het gevolg hebben. Lees meer hierover in deze "email":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2006-March/000512.html.
-Naast de upload is Ari Pollak bij ons team gekomen en heeft
-"rcov":http://www.eigenclass.org/hiki.rb?cmd=view&p=rcov toegevoegd aan
-onze lijst van team-beheerd gereedschap en bibliotheken. Andere paketten
-die toegevoegd zijn in de laaste drie maanden zijn:
-"libgpgme-ruby":http://packages.debian.org/unstable/libs/libgpgme-ruby,
-"librmagick-ruby":http://packages.debian.org/unstable/interpreters/librmagick-ruby,
-"liblog4r-ruby":http://packages.debian.org/unstable/devel/liblog4r-ruby,
-"libgnuplot-ruby":http://packages.debian.org/unstable/libs/libgnuplot-ruby,
-"feed2imap":http://packages.debian.org/unstable/net/feed2imap,
-"libjson-ruby":http://packages.debian.org/unstable/interpreters/libjson-ruby
- en
-"libcairo-ruby":http://packages.debian.org/unstable/libs/libcairo-ruby.
-_(paulvt)_
+Naast de upload is Ari Pollak bij ons team gekomen en heeft "rcov":http://www.eigenclass.org/hiki.rb?cmd=view&p=rcov toegevoegd aan onze lijst van team-beheerd gereedschap en bibliotheken. Andere paketten die toegevoegd zijn in de laaste drie maanden zijn: "libgpgme-ruby":http://packages.debian.org/unstable/libs/libgpgme-ruby, "librmagick-ruby":http://packages.debian.org/unstable/interpreters/librmagick-ruby, "liblog4r-ruby":http://packages.debian.org/unstable/devel/liblog4r-ruby, "libgnuplot-ruby":http://packages.debian.org/unstable/libs/libgnuplot-ruby, "feed2imap":http://packages.debian.org/unstable/net/feed2imap, "libjson-ruby":http://packages.debian.org/unstable/interpreters/libjson-ruby
+ en "libcairo-ruby":http://packages.debian.org/unstable/libs/libcairo-ruby. _(paulvt)_
h3. 01.01.2006 - Nieuw lid, @dh_rdoc@
-Er is een nieuw lid aan het team toegevoegd: Thierry Reding. Welcome!
-Ondertussen is Esteban Manchado Velázquez begonnen aan het implementeren van
-"@dh_rdoc@":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wiki/index.cgi?DocumentationGeneration. _(paulvt)_
+Er is een nieuw lid aan het team toegevoegd: Thierry Reding. Welcome! Ondertussen is Esteban Manchado Velázquez begonnen aan het implementeren van "@dh_rdoc@":http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wiki/index.cgi?DocumentationGeneration. _(paulvt)_
h3. 02.11.2005 - Nieuwe teamleden
-Ons "team":https://alioth.debian.org/project/memberlist.php?group_id=30665
-is de laatste versterkt door een groep mensen. Deze groep bestaat uit de
-volgende developers-to-be: Daigo Moriwaki, Lucas Nussbaum and Arnaud
-Cornet. We hopen dat wij als team binnenkort een verschil kunnen maken op
-het gebied van Ruby bibliotheek en applicatie beheer. Wordt vervolgd...
-_(paulvt)_
+Ons "team":https://alioth.debian.org/project/memberlist.php?group_id=30665 is de laatste versterkt door een groep mensen. Deze groep bestaat uit de volgende developers-to-be: Daigo Moriwaki, Lucas Nussbaum and Arnaud Cornet. We hopen dat wij als team binnenkort een verschil kunnen maken op het gebied van Ruby bibliotheek en applicatie beheer. Wordt vervolgd... _(paulvt)_
-
h3. 27.09.2005 - Toevoeging van @libxml-ruby@ en @libxslt-ruby@
-Wegens een recent "verzoek om
-adoptie":http://lists.debian.org/debian-devel/2005/09/msg00854.html van
- at libxml-ruby@ en @libxslt-ruby@, heb ik besloten om beide bibliotheken te
-adopteren en ze toe te voegen aan pkg-ruby-extras. Hiermee hoop ik de
-aanwezigheid van meer bron-pakketten die door het team beheerd worden te
-vergroten. Dit volgt dan op het vorige @ruby-pkg-tools@ pakket dat al in
-het archief zit. _(damog)_
+Wegens een recent "verzoek om adoptie":http://lists.debian.org/debian-devel/2005/09/msg00854.html van @libxml-ruby@ en @libxslt-ruby@, heb ik besloten om beide bibliotheken te adopteren en ze toe te voegen aan pkg-ruby-extras. Hiermee hoop ik de aanwezigheid van meer bron-pakketten die door het team beheerd worden te vergroten. Dit volgt dan op het vorige @ruby-pkg-tools@ pakket dat al in het archief zit. _(damog)_
h3. 03.09.2005 - Geïntegreerde Wiki
-Ik heb "Kwiki":http://www.kwiki.org/ toegevoegd aan de website opstelling
-en het "geïntegreerd":/cgi-bin/wiki/index.cgi in deze pagina via de
-pagina specifieke WikiLinks. _(paulvt)_
+Ik heb "Kwiki":http://www.kwiki.org/ toegevoegd aan de website opstelling en het "geïntegreerd":/cgi-bin/wiki/index.cgi in deze pagina via de pagina specifieke WikiLinks.
+_(paulvt)_
h3. 01.09.2005 - @ruby-pkg-tools@ is in het archief geaccepteerd
-Het @ruby-pkg-tools@ pakket (versie 0.1) is zojuist geaccepteerd en is dus
-door de ``new queue'' heen. Dit betekent dat @ruby-pkg-tools@ vanavond
-beschikbaar zal zijn en dat Ruby pakketten dit kunnen gaan
-"gebruiken":ruby-pkg-tools/index.html. _(paulvt)_
+Het @ruby-pkg-tools@ pakket (versie 0.1) is zojuist geaccepteerd en is dus door de ``new queue'' heen. Dit betekent dat @ruby-pkg-tools@ vanavond beschikbaar zal zijn en dat Ruby pakketten dit kunnen gaan "gebruiken":ruby-pkg-tools/index.html. _(paulvt)_
h3. 29.08.2005 - Eerst website poging
-Ik heb zojuist een eerste website versie van het Debian/Ruby Extra's team
-online gezet. De bron-bestanden zullen binnenkort in Subversion arriveren,
-opdat iedereen deze kan aanpassen en aanvullen. _(paulvt)_
+Ik heb zojuist een eerste website versie van het Debian/Ruby Extra's team online gezet. De bron-bestanden zullen binnenkort in Subversion arriveren, opdat iedereen deze kan aanpassen en aanvullen. _(paulvt)_
Modified: website/src/10.join.en.page
===================================================================
--- website/src/10.join.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/10.join.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -4,28 +4,16 @@
---
h2. How to Join the Team?
-We always welcome people to help us out. If you want to, please
-follow the following guidelines.
+We always welcome people to help us out. If you want to, please follow the following guidelines.
-* Contact us first on our
- "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 (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) and mention the addition
- in the changelog. For example:
+* Contact us first on our "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 (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) and mention the addition in the changelog. For example:
<pre><code>
$ svn co svn+ssh://LOGIN@svn.debian.org/svn/pkg-ruby-extras/tools/ruby-pkg-tools/trunk/
$ cd trunk
$ vi pkg-ruby-extras.team debian/changelog
$ svn commit -m "add NAME to the team"
</code></pre>
- This package will be uploaded once there are more
- significant changes. Please do not forget to add a comma at the end of
- the previous line, as this would break generated control files.
+ This package will be uploaded once there are more significant changes. Please do not forget to add a comma at the end of the previous line, as this would break generated control files.
Modified: website/src/30.subversion.en.page
===================================================================
--- website/src/30.subversion.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/30.subversion.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -6,13 +6,11 @@
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.
+If you need general help with Subversion, an "online book":http://svnbook.red-bean.com/ is available.
h3. Repository structure
-Our "repository":http://svn.debian.org/wsvn/pkg-ruby-extras/
-is structured like this:
+Our "repository":http://svn.debian.org/wsvn/pkg-ruby-extras/ is structured like this:
<pre><code>pkg-ruby-extras
+-- packages
@@ -28,27 +26,18 @@
+-- website
+-- ...</code></pre>
-All our packages will live inside the @packages/@ and @packages-wip/@
-directories. @packages-wip/@ contains packages which have not been uploaded to
-Debian yet (WIP stands for Work In Progress), and packages are moved to
- at packages/@ after their first upload. Each package directory will have a
-structure common to subversion-managed projects:
+All our packages will live inside the @packages/@ and @packages-wip/@ directories. @packages-wip/@ contains packages which have not been uploaded to Debian yet (WIP stands for Work In Progress), and packages are moved to @packages/@ after their first upload. 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/.
+ 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:
+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
@@ -66,8 +55,7 @@
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.
+*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
@@ -105,32 +93,24 @@
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@):
+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 . You can also optionally use
- at debcommit -r@ if you have the devscripts package installed.
+Alternatively, you can tell @svn-buildpackage@ to automatically tag the release after building using the option @--svn-tag at . You can also optionally use @debcommit -r@ if you have the devscripts package installed.
-*Attention:* use this option only when you are sure that this build will
-be the final build, just before upload.
+*Attention:* use this option only when you are sure that this build will be the final build, just before upload.
h3. Package upload checklist
# Update your repository (just in case).
# Rebuild the package (without @--svn-ignore-new@!).
# Check everything is alright and do whatever tests you always do.
-# Change the latest changelog entry distribution to "unstable" (or whatever is
- appropriate).
+# Change the latest changelog entry distribution to "unstable" (or whatever is appropriate).
# Rebuild again _with_ @pbuilder@!
# Perform small checks, final @lintian@ & @linda@ check.
# Upload the package.
# Tag with @svn-buildpackage --svn-tag-only at .
# Commit the new changelog entry for the @UNRELEASED@ distribution.
-We will soon release a bash source file with useful aliases. If you are
-interested, write to our mailing list, @pkg-ruby-extras-maintainers@ (at
- at lists.alioth.debian.org@).
+We will soon release a bash source file with useful aliases. If you are interested, write to our mailing list, @pkg-ruby-extras-maintainers@ (at @lists.alioth.debian.org@).
Modified: website/src/35.policy.en.page
===================================================================
--- website/src/35.policy.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/35.policy.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -4,12 +4,9 @@
---
h1. Debian Ruby Policy
-*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.
-* "Debian Python Policy":http://www.debian.org/doc/packaging-manuals/python-policy/:
- an interesting read, since Python shares several problems with Ruby.
+*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.
+* "Debian Python Policy":http://www.debian.org/doc/packaging-manuals/python-policy/: an interesting read, since Python shares several problems with Ruby.
h2. Packaging Variants
@@ -21,21 +18,15 @@
h3. Support only the default Ruby version
* Name you package @libfoo-ruby at .
-* Depend on @ruby (>= 1.X)@, @ruby (<< 1.X+1)@ (you will trigger a conflict
- when the default Ruby version is changed, so you will have to provide a
- new version ASAP, since your package will block the upgrade of Ruby).
+* Depend on @ruby (>= 1.X)@, @ruby (<< 1.X+1)@ (you will trigger a conflict when the default Ruby version is changed, so you will have to provide a new version ASAP, since your package will block the upgrade of Ruby).
h3. Support several Ruby versions
-* Create a package @libfoo-ruby@ which depends on @libfoo-ruby1.X@ (@1.X@ being
- the default Ruby version).
-* Create @libfoo-ruby1.X@, @libfoo-ruby1.Y@ for each Ruby version you want
- to support.
+* Create a package @libfoo-ruby@ which depends on @libfoo-ruby1.X@ (@1.X@ being the default Ruby version).
+* Create @libfoo-ruby1.X@, @libfoo-ruby1.Y@ for each Ruby version you want to support.
h2. Documentation and Examples
-* If the documentation for your library is small enough, put in in
- @libfoo-ruby@ (even if you are supporting several Ruby versions).
+* If the documentation for your library is small enough, put in in @libfoo-ruby@ (even if you are supporting several Ruby versions).
-* If the documentation is too big, provide it in @libfoo-ruby-doc@, and
- make all other packages suggest @libfoo-ruby-doc at .
+* If the documentation is too big, provide it in @libfoo-ruby-doc@, and make all other packages suggest @libfoo-ruby-doc at .
Modified: website/src/40.rubygems.en.page
===================================================================
--- website/src/40.rubygems.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/40.rubygems.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -4,59 +4,27 @@
---
h1. Position on RubyGems
-The Debian pkg-ruby-extras team takes care of the packaging of third-party
-libraries (not shipped in the standard library). We describe here our position
-on RubyGems.
+The Debian pkg-ruby-extras team takes care of the packaging of third-party libraries (not shipped in the standard library). We describe here our position on RubyGems.
-"RubyGems":http://docs.rubygems.org/ has become the standard way to distribute
-and install Ruby libraries. It allows developers of libraries to distribute
-their work, and install the latest version of other libraries in an
-easy-to-install and cross-platform way, without intermediaries (like Linux
-distributions' packaging systems). RubyGems is thus clearly a very useful tool,
-from the developer point-of-view. Some other languages have similar tools, like
-"Perl's CPAN":http://www.cpan.org/, and "Python's
-eggs":http://peak.telecommunity.com/DevCenter/PythonEggs.
+"RubyGems":http://docs.rubygems.org/ has become the standard way to distribute and install Ruby libraries. It allows developers of libraries to distribute their work, and install the latest version of other libraries in an easy-to-install and cross-platform way, without intermediaries (like Linux distributions' packaging systems). RubyGems is thus clearly a very useful tool, from the developer point-of-view. Some other languages have similar tools, like "Perl's CPAN":http://www.cpan.org/, and "Python's eggs":http://peak.telecommunity.com/DevCenter/PythonEggs.
-However, users (both end users of classic applications, and system
-administrators who will install web applications) have different needs. Most of
-them want their ruby applications to be installable in the same way as their
-other applications, which usually means using their Linux distribution's
-package manager. The installation of ruby applications could then use
-existing infrastructure (local proxies, for example), and security updates
-would be tracked with the same tools.
+However, users (both end users of classic applications, and system administrators who will install web applications) have different needs. Most of them want their ruby applications to be installable in the same way as their other applications, which usually means using their Linux distribution's package manager. The installation of ruby applications could then use existing infrastructure (local proxies, for example), and security updates would be tracked with the same tools.
-Unfortunately, while other languages promote good practices that make manual
-installation and packaging of libraries very easy (Perl's Makefile.pl,
-Python's distutils), the Ruby community tends to impose the use of RubyGems for
-everyone: it is currently impossible to install most Ruby applications
-(Rails-based applications, for example) without using RubyGems.
+Unfortunately, while other languages promote good practices that make manual installation and packaging of libraries very easy (Perl's Makefile.pl, Python's distutils), the Ruby community tends to impose the use of RubyGems for everyone: it is currently impossible to install most Ruby applications (Rails-based applications, for example) without using RubyGems.
We ask Ruby developers to:
-* continue to provide RubyGems for their software, as they are useful for other
-Ruby developers who need latest versions of their software.
+* continue to provide RubyGems for their software, as they are useful for other Ruby developers who need latest versions of their software.
-* also provide their software in a format suitable for manual installation and
-packaging. For more information on specific problems we encounter with Ruby software, and how to solve them, please see "this page":upstream-devs.html
+* also provide their software in a format suitable for manual installation and packaging. For more information on specific problems we encounter with Ruby software, and how to solve them, please see "this page":upstream-devs.html h2. RubyGems package in Debian
-h2. RubyGems package in Debian
+A "rubygems package":http://packages.debian.org/sid/rubygems is provided in Debian. It is aimed at developers willing to install bleeding edge library versions, or libraries that have not yet been packaged in Debian. This package provides the gem command to be able to install/remove gems at the developer's own discretion and risk. The gems will be installed using the normal gem installation procedure, under /var/lib/gems, as the normal Gem installation path is incompatible with the "FHS":http://www.pathname.com/fhs/.
-A "rubygems package":http://packages.debian.org/sid/rubygems is provided in
-Debian. It is aimed at developers willing to install bleeding edge library
-versions, or libraries that have not yet been packaged in Debian. This package
-provides the gem command to be able to install/remove gems at the developer's
-own discretion and risk. The gems will be installed using the normal gem
-installation procedure, under /var/lib/gems, as the normal Gem installation
-path is incompatible with the "FHS":http://www.pathname.com/fhs/.
-
This package must not be used to create or build Debian packages.
h2. Contact information
-The Debian pkg-ruby-extras team can be contacted at
- at pkg-ruby-extras-maintainers AT lists.alioth.debian.org at . In particular, feel
-free to send comments or questions about this document, or suggest Ruby
-libraries that we should package in Debian.
+The Debian pkg-ruby-extras team can be contacted at @pkg-ruby-extras-maintainers AT lists.alioth.debian.org at . In particular, feel free to send comments or questions about this document, or suggest Ruby libraries that we should package in Debian.
h2. Some links
Modified: website/src/50.upstream-devs.en.page
===================================================================
--- website/src/50.upstream-devs.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/50.upstream-devs.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -6,27 +6,19 @@
Dear developer,
-Your library/application is very good, and we would like to integrate it
-into our favorite distribution, so many more people would benefit easily
-from it. However, it would be great if you could make our work as easy as
-possible by following those guidelines.
+Your library/application is very good, and we would like to integrate it into our favorite distribution, so many more people would benefit easily from it. However, it would be great if you could make our work as easy as possible by following those guidelines.
h3. Distribute your software as a source code archive
"RubyGems":http://docs.rubygems.org/ is a useful tool for developers, but isn't a good tool for the general distribution of your software (see "this page":rubygems.html for more information).
-Distribute your software as a @.tar.gz@ archive. @.tar.gz@ is the most widely
-used archive format on Linux. Using other formats (@.tar.bz2@, for example) is
-discouraged, as it requires additional steps for the packager. A @.zip@ file
-could be provided for Windows users.
+Distribute your software as a @.tar.gz@ archive. @.tar.gz@ is the most widely used archive format on Linux. Using other formats (@.tar.bz2@, for example) is discouraged, as it requires additional steps for the packager. A @.zip@ file could be provided for Windows users.
Including the version of the software in the name of the archive is also a very good idea.
h3. Use @setup.rb@
-Provide a "setup.rb":http://i.loveruby.net/en/projects/setup/. Use it with its
-default layout (@bin/@, @lib/@, ...). Test that your software works when
-installed using it.
+Provide a "setup.rb":http://i.loveruby.net/en/projects/setup/. Use it with its default layout (@bin/@, @lib/@, ...). Test that your software works when installed using it.
If your library is only a native library, using @extconf.rb@ might be a suitable alternative. However, all extconf use-cases are covered by @setup.rb at .
@@ -34,8 +26,7 @@
h3. Remove all references to rubygems in the software you ship
-One big issue we have with rubygems is that it is source-intrusive: developers add
- at require 'rubygems'@ in their code, which:
+One big issue we have with rubygems is that it is source-intrusive: developers add @require 'rubygems'@ in their code, which:
* fails if the user doesn't have rubygems installed
* causes manually-installed (or installed with a package manager) libraries to be ignored after RubyGems has been loaded.
@@ -48,16 +39,14 @@
</pre></code>
As this will succeed on systems with rubygems installed.
-Instead, make the loading of rubygems conditional, using a global constant that
-you can easily disable before releasing:
+Instead, make the loading of rubygems conditional, using a global constant that you can easily disable before releasing:
<code><pre>require 'rubygems' if DEVELOPER_MODE</pre></code>
For the same reason, @require_gem@ must not be used.
h3. Don't make your Rakefile depend on RubyGems
-If you provide a Rakefile, make sure it is usable without RubyGems
-installed. The following example is known to work:
+If you provide a Rakefile, make sure it is usable without RubyGems installed. The following example is known to work:
<code><pre>require 'rake/testtask'
require 'rake/packagetask'
require 'rake/rdoctask'
@@ -102,7 +91,6 @@
rd.options << '--all'
end
-
Rake::PackageTask.new(PKG_NAME, PKG_VERSION) do |p|
p.need_tar = true
p.package_files = PKG_FILES
@@ -133,28 +121,20 @@
h3. Make your tests and examples usable outside of your directory tree
-*Do not* do things like <code>require '../lib/yourpackagename'</code>.
-Instead, use the following example:
+*Do not* do things like <code>require '../lib/yourpackagename'</code>. Instead, use the following example:
<code><pre>$:.unshift '../lib'
require 'yourpackagename'</pre></code>
-This way, example and test scripts can be moved to other locations, but
-will still be able to use the global installation of your library. And
-since '../lib' is added at the beginning of the search patch, you will be
-able to use the version of your library you are working on during
-development.
+This way, example and test scripts can be moved to other locations, but will still be able to use the global installation of your library. And since '../lib' is added at the beginning of the search patch, you will be able to use the version of your library you are working on during development.
h3. Use a shebang that works everywhere
-The Ruby interpreter can be installed in different places. Instead of
-using <code>#!/usr/bin/ruby</code> or <code>#!/usr/local/bin/ruby</code>,
-use <code>#!/usr/bin/env ruby</code>.
+The Ruby interpreter can be installed in different places. Instead of using <code>#!/usr/bin/ruby</code> or <code>#!/usr/local/bin/ruby</code>, use <code>#!/usr/bin/env ruby</code>.
h3. Provide man pages for your binaries
-Some distributions (e.g. Debian) require all executables to have a man page.
-It would be great if you could provide it yourself.
+Some distributions (e.g. Debian) require all executables to have a man page. It would be great if you could provide it yourself.
h3. If possible, maintain a backward-compatible API
@@ -167,7 +147,4 @@
h2. Contact information
-The Debian pkg-ruby-extras team can be contacted at
- at pkg-ruby-extras-maintainers AT lists.alioth.debian.org at . In particular, feel
-free to send comments or questions about this document, or suggest Ruby
-libraries that we should package in Debian.
+The Debian pkg-ruby-extras team can be contacted at @pkg-ruby-extras-maintainers AT lists.alioth.debian.org at . In particular, feel free to send comments or questions about this document, or suggest Ruby libraries that we should package in Debian.
Modified: website/src/ruby-pkg-tools/00.index.en.page
===================================================================
--- website/src/ruby-pkg-tools/00.index.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/ruby-pkg-tools/00.index.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -5,23 +5,10 @@
---
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 in Debian.
-It contains the following:
+Most of the packaging work can be simplified using the Ruby Package Tools. The tools are contained in the @ruby-pkg-tools@ package, available in Debian. It contains the following:
-* A "file":team-members.html (@pkg-ruby-extras.team@) containing the names and email addresses
- of all team members.
-* 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.html (@uploaders.mk@) to perform a substitution on build-time,
- filling in the Uploaders field with the team members. *NB*: this
- rule has been deprecated, *do not use*.
+* A "file":team-members.html (@pkg-ruby-extras.team@) containing the names and email addresses of all team members.
+* 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.html (@uploaders.mk@) to perform a substitution on build-time, filling in the Uploaders field with the team members. *NB*: this rule has been deprecated, *do not use*.
* 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.
+* 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.
Modified: website/src/ruby-pkg-tools/20.team-members.en.page
===================================================================
--- website/src/ruby-pkg-tools/20.team-members.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/ruby-pkg-tools/20.team-members.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -4,10 +4,6 @@
---
h2. The Team Member List
-A list of team members of the Debian Ruby Extras Maintainers is kept in
-@/usr/share/ruby-pkg-tools/pkg-ruby-extras.team at . If you have joined the
-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.
+A list of team members of the Debian Ruby Extras Maintainers is kept in @/usr/share/ruby-pkg-tools/pkg-ruby-extras.team at . If you have joined the 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 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/ruby-pkg-tools/30.cdbs.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -4,18 +4,11 @@
---
h2. The CDBS Classes
-The tools includes two CDBS classes, @ruby-setup-rb.mk@ and
- at ruby-extconf-rb.mk@, for automating the building of a package for upstream
-source that uses @install.rb@, @setup.rb@ or @extconf.rb@ as
-builder/installer. The classes try to create a package that adheres to the
-Debian/Ruby policy ("draft
-version":http://pkg-ruby.alioth.debian.org/ruby-policy.html/index.html) and
-takes a lot of common standard and often the same work out of your hands.
+The tools includes two CDBS classes, @ruby-setup-rb.mk@ and @ruby-extconf-rb.mk@, for automating the building of a package for upstream source that uses @install.rb@, @setup.rb@ or @extconf.rb@ as builder/installer. The classes try to create a package that adheres to the Debian/Ruby policy ("draft version":http://pkg-ruby.alioth.debian.org/ruby-policy.html/index.html) and takes a lot of common standard and often the same work out of your hands.
h3. Basic usage
-A common @debian/rules@ file for @setup.rb@ using this @ruby-setup-rb@
-class would look like this:
+A common @debian/rules@ file for @setup.rb@ using this @ruby-setup-rb@ class would look like this:
<pre><code>#!/usr/bin/make -f
#
@@ -35,13 +28,9 @@
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/ruby-pkg-tools/1/class/ruby-extconf-rb.mk</code></pre>
-You can have a look at @libgpgme-ruby@ to see how an @extconf.rb@ based
-package can be built.
+You can have a look at @libgpgme-ruby@ to see how an @extconf.rb@ based package can be built.
-Note that it is still possible to configure and override the behaviour of
-the class and debhelper. No control is lost. For more information about
-how to use the class, see the "CDBS
-HOWTO":https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml.
+Note that it is still possible to configure and override the behaviour of the class and debhelper. No control is lost. For more information about how to use the class, see the "CDBS HOWTO":https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml.
*N.B.* When using either of these classes, don't forget to add
* "debhelper" and "cdbs" to the Build-Depends field
Modified: website/src/ruby-pkg-tools/40.uploaders.en.page
===================================================================
--- website/src/ruby-pkg-tools/40.uploaders.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/ruby-pkg-tools/40.uploaders.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -4,8 +4,4 @@
---
h2. The Uploaders Rule
-Some time ago, we used to write the name of all the members of the
-team in the @Uploaders@ control field. This has been argued against
-"here":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2007-February/001426.html.
-Please, do not use @uploaders.mk@ anymore. Uploaders should only be
-people who made significant changes to the package.
+Some time ago, we used to write the name of all the members of the team in the @Uploaders@ control field. This has been argued against "here":http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2007-February/001426.html. Please, do not use @uploaders.mk@ anymore. Uploaders should only be people who made significant changes to the package.
Modified: website/src/ruby-pkg-tools/50.sources.en.page
===================================================================
--- website/src/ruby-pkg-tools/50.sources.en.page 2009-05-05 10:18:30 UTC (rev 3505)
+++ website/src/ruby-pkg-tools/50.sources.en.page 2009-05-05 11:16:17 UTC (rev 3506)
@@ -4,16 +4,11 @@
---
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; it can use either the @pkg-ruby-extras.sources@ information
-file or (preferably) the package's @debian/watch@ file.
+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; it can use either the @pkg-ruby-extras.sources@ information file or (preferably) the package's @debian/watch@ file.
h3. Basic usage
-A basic usage scenario for @pkg-ruby-get-sources@ is to do a checkout,
-get the upstream source and build:
+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
@@ -26,10 +21,7 @@
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 .
+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?
@@ -39,13 +31,9 @@
h3. @debian/watch@ files
-This is by far the best way to do, as other tools from debian also use the information
-stored in this file (see for instance "QA pages for developers":http://qa.debian.org/developer.php).
+This is by far the best way to do, as other tools from debian also use the information stored in this file (see for instance "QA pages for developers":http://qa.debian.org/developer.php).
-The principle is simple: if the software you package provides a web page with a link to source tarballs,
-all you need to do is provide the location of this page along with a regular expression matching
-the *link* to the tarball. For a standard "Rubyforge":http://rubyforge.org package, the watchfile
-would look like
+The principle is simple: if the software you package provides a web page with a link to source tarballs, all you need to do is provide the location of this page along with a regular expression matching the *link* to the tarball. For a standard "Rubyforge":http://rubyforge.org package, the watchfile would look like
<pre><code>version=3
http://rubyforge.org/frs/?group_id=701 .*tioga-([\d.-]*)\.t.*</code></pre>
@@ -76,8 +64,4 @@
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@).
+ 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-commits
mailing list