[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Ruby packaging in wheezy: gem2deb, new policy, etc.



Lucas Nussbaum escreveu isso aí:
> On 30/01/11 at 22:20 -0300, Antonio Terceiro wrote:
> > Lucas Nussbaum escreveu isso aí:
> > > > a) only native code:
> > > > 
> > > >   Packages: ruby1.8-foo, ruby-1.9.1 etc
> > > > 
> > > >   All of them must provide ruby-foo
> > > > 
> > > > b) both pure-ruby and native code
> > > > 
> > > >   Packages:
> > > >     ruby-foo      - contains pure-ruby code
> > > >     ruby1.8-foo   - contains native code for ruby1.8
> > > >     ruby1.9.1-foo - contains native code for ruby1.9.1
> > > > 
> > > >   ruby1.8-foo and ruby1.9.1-foo (etc) depend on ruby-foo
> > > > 
> > > >   ruby-foo depend on the version for the default interpreter (so that
> > > >   installing ruby-foo will get you something that words) 
> > > 
> > > I think that we should go for this.
> > [...]
> > > Could you update the Wiki page? :-)
> 
> Note that this creates a dependency loop. I'm not sure if that's
> considered bad or not.

Yes, I explicitly noted that when I updated the wiki page. I guess this
circular dependency is not critical since it is a very short cycle in
the dependency graph (A depends on B or C; B and C depend on A). I also
don't see a sane way to avoid this type of dependency in our case.

> > I still have one doubt, that's with the following statement: "libraries
> > depend on '''ruby-foo'''". I am not sure what we mean with that, and we
> > should probably think of all the possibilities:
> > 
> > pure-Ruby/pure-native/mixed package depends on 
> > pure-Ruby/pure-native/mixed package
> > 
> > There are 9 combinations. Probably most of them can be handled
> > uniformly, but some of them will bring trouble. Let's think about it.
> > :)
> 
> I think that pure-native and mixed are the same. So we are down to 4
> cases;)
> 
> pure depends on pure -> simple dep on ruby-foo
> pure depends on native -> I would stay: simple-dep on ruby-foo. People
> can install ruby1.9.1-foo foo if they want additional support
> 
> common package for native (ruby-foo) depends on pure -> simple, depend on ruby-foo
> common package for native (ruby-foo) depends on native -> depend on ruby-foo
> 
> arch-specific package for native depends on pure -> simple, depend on ruby-foo
> arch-specific package for native depends on native -> depend on
> rubyXXX-foo
> 
> Would that work?

I guess it would. In the end, the only special case is 'native depends on
native'. I've updated the wiki accordingly.

-- 
Antonio Terceiro <terceiro@softwarelivre.org>
http://softwarelivre.org/terceiro


Attachment: signature.asc
Description: Digital signature


Reply to: