At 12:42 Uhr -0500 07.03.2002, Benjamin Reed wrote:
>Max Horn [max@...] wrote:
>> I just added code to CVS that enables initial splitoff support. All
>> brave developers please go ahead and install it and test how it
>> works. To do so, check out the "fink" CVS module and use the
>> inject.pl script.
>Other than my libtool versioning issue (which isn't fink's fault),
>I've had 0 problems converting my rrdtool package over to splitoff
>format -- it works great. Thanks, Max!
>One question it does bring up, that I remember being mentioned before,
>is that of library dependencies. Right now I have them set up with
>dependencies like so, which was what I saw in examples when we were
>first doing separate shlibs packages:
> Depends: %N-shlibs (>= %v-%r)
> Replaces: %N (<< %v-%r)
> Suggests: %N-bin
> Replaces: rrdtool (<< %v-%r)
> Depends: %N (>= %v-%r)
>dpkg will install multiple versions of rrdtool-shlibs, right?
No. There can never be multiple versions of the same package being
installed at once.
>But right now, we have no way of really planning ahead for a
>version that's too high, like, if rrdtool version 2 is out.
If you ever get an incompatible version, then you would change the
name of the -shlibs package to e.g. "rrdtool2-shlibs". Old packages
would still use the old rrdtool-shlibs while new could take advantage
of the new version.
This will become especially nice once the 3rd (or was it 4th? :-)
stage of the shlibs plan is reached - at this stage, Fink will
autoamtically detect if a lib links against a given shared lib and
automatically add the packages providing that shared lib to the
dependencies of the package being built.
>If someone makes a package that links against librrd.1, what
>do they put as depends?
>If they make it "rrdtool-shlibs (>= %v-%r)" then rrdtool-shlibs
>2.0.0-1 would match, and it would happily upgrade and break
>things on an update-all.
Yeah, that's why you have to use a different package name then.
>In the RPM world, RPMs automatically "provide" any librrd.*
>files, and then interrogate all of the binaries of a package and
>determine what libraries they need and add them as Depends.
>I'm pretty sure debian's package stuff do the same thing, but
>I don't have as much experience with them.
Yes they do it. You should read up in the fink-devel list archives
>Is this something that needs to be reexamined now that split packages
>are a reality?
No. Look at the fink-devel archives, and also at the various docs in
the "shared-libraries" CVS module.
phone: (+49) 6151-494890