[DRE-maint] RFS: ruby-omniauth

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> On 27/08/11 at 03:08 +0530, Muneeb Shaikh wrote:
> > Dear mentors,
> > 
> > I am looking for a sponsor for my package "ruby-omniauth".
> > 
> >  * Package name    : ruby-omniauth
> >    Version         : 0.2.6-1
> >    Upstream Author : Michael Bleigh <michael at intridea.com>,
> >                      Erik Michaels-Ober <sferik at gmail.com>
> > 
> >  * URL             : http://github.com/intridea/omniauth
> >  * License         : MIT
> >    Section         : ruby
> > 
> > It builds those binary packages:
> > 
> > ruby-omniauth - Rack middleware for standardized multi-provider
> > authentication
> > 
> > To access further information about this package, please visit the
> > following URL:
> > 
> >   http://mentors.debian.net/package/ruby-omniauth
> > 
> > Alternatively, one can download the package with dget using this command:
> > 
> >   dget -x
> > http://mentors.debian.net/debian/pool/main/r/ruby-omniauth/ruby-omniauth_0.2.6-1.dsc
> > 
> > I would be glad if someone uploaded this package for me.
> 
> Hi,
> 
> The gem has dependencies on oa-basic (= 0.2.6), oa-enterprise (=
> 0.2.6), oa-core (= 0.2.6), oa-more (= 0.2.6), oa-oauth (= 0.2.6),
> oa-openid (= 0.2.6). Are you sure that the package can work standalone
> like that?
> If it's the case, please remove the commented line in debian/control

I doubt it will work the way it is now:

$ cat lib/omniauth.rb
require 'omniauth/core'
require 'omniauth/basic'
require 'omniauth/oauth'
require 'omniauth/openid'
require 'omniauth/enterprise'
require 'omniauth/more'

> Ah, now I see that the package builds several gems. I don't think that
> it's a layout that we support at the moment, so it might require changes
> in gem2deb itself. Antonio, what do you think?

I'm not sure yet about the best way to support this, or even about
supporting it directly at all. The problem is that each package has a
different strategy for implementing multiple package.

For example this one package has both code under lib/ _and_ subpackages
under subdirectories. What I would do is keep using gem2deb but add a
special installation step before the default gem2deb installation step,
something like this:

  PACKAGES = \
    oa-basic \
    oa-core \
    oa-enterprise \
    oa-more \
    oa-oauth \
    oa-openid

  override_dh_auto_install:
    for pkg in $(PACKAGES); do dh_install -p ruby-$$pkg $$pkg/lib/*  /usr/lib/ruby/vendor_ruby; done
    dh_auto_install

Of course, you will need to add the appropriate binary package stanzas
to debian/control, and check the dependencies for each sub-package, and
make sure the tests for all of them are run during package build.

-- 
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20110827/4ef6f536/attachment.pgp>