On Wed, Jan 21, 2004 at 09:10:24AM +0100, Michal 'hramrach' Suchanek wrote:
> On Tue, Jan 20, 2004 at 04:39:27AM -0500, Daniel Macks wrote:
> > On Tue, Jan 20, 2004 at 10:22:04AM +0100, Michal 'hramrach' Suchanek wrote:
> > > On Mon, Jan 19, 2004 at 10:28:33PM -0500, Daniel Macks wrote:
> > > > On Mon, Jan 19, 2004 at 01:35:31PM +0100, Michal Suchanek wrote:
> > > >
> > > > > So I made ripper-ruby16 0.0.5-2 that has a splitoff ripper
> > > > > 0.0.5-2-16, ripper-ruby18 with splitoff ripper 0.0.5-2-18, etc.
> > > >
> > > > What exactly is the purpose of these splitoffs and what do they
> > > > contain? [...]
> > > > are you trying to arrange so that other fink packages can use yours
> > > > by simply "Depends: ripper" and be assured of a fully functional
> > > > module *somewhere*?
> > > Yes, that's what I intended to do.
> >
> > Okay then, I have to ask: why?
> It was the first soulotion that came to my mind and I like it.
Valid, so long as it works.
Given that they won't know where, though, what's the point? I'm
thinking back to your example of an invalid configuration:
> ruby16 + ruby18 + ruby 1.8.0 + ripper-ruby16 + fxruby-ruby18 + freeride
that could result from freeride saying 'Depends: ripper, fxruby'.
Experience has shown that when we have foo-pmXX provides:foo-pm (or a
foo-pm bundle depends:foo-pmXX|foo-pmYY) other package maintainers are
likely to Depends:foo-pm without considering that it's the same as
your broken example.
> > > > Based on the freeride example you give, you're in the same
> > > > versioned-perl-module handbasket. If it's the freeride package (which
> > > > is not ruby-versioned) that needs a certain suite of modules all in
> > > > the "same ruby-version", it's up to that package to request them. Why
> > > > can't it just pick a ruby and use it?
> > >
> > > As you put it it should be possible to make
> > > freeride + freeride-ruby18 + freeride-ruby16 where freeride-rubyXX contains a
> > > script for running freeride with the correct interpreter.
If that's the case for this example:
> I had another thing in mind:
>
> Package: freeride
> Depends: freeride-ruby-runtime
> (contains the freeride sources)
>
> Package: freeride-ruby16
> Depends: ruby16, ripper-ruby16, fxruby-ruby16
> Provides: freeride-ruby-runtime
> (contains a startup script)
Which I would assume looks like:
freeride: %p/bin/freeride-bin (some script)
freeride-ruby16: %p/bin/freeride ('%p/bin/ruby1.6 %p/bin/freeride-bin')
So you'd need freeride-ruby16 Depends:freeride-ruby16, which causes a
dependency loop. I have no idea whether freeride-ruby16 also has
things that other programs might want (i.e., would someone ever want
to install freeride-ruby16 and -ruby18 at the same time?), but if so
then there are file conflicts.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
