Max Horn [[EMAIL PROTECTED]] wrote:
> >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.
In this case, would it maybe make more sense to make even version
1 packages have the number in them, and then make a versionless
wrapper package that will get the latest one:
rrdtool:
Depends: rrdtool1
rrdtool1:
Depends: rrdtool1-shlibs
...otherwise, when rrdtool 2.0 comes out, someone who doesn't know
any better will be accidentally pulling the old version, because
they assumed they should do "apt-get install rrdtool" to get
rrdtool. I only bring it up now because it would save a lot of
time in the long run if it needs to become a naming convention
eventually...
> 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.
...
> No. Look at the fink-devel archives, and also at the various docs in
> the "shared-libraries" CVS module.
This is what I had missed... I remember the original discussions but
hadn't seen it come back up. I totally missed the existence of the
"shared-libraries" module, which (gasp!) documents the gameplan...
Sorry about bugging you... =)
--
Ben Reed a.k.a. Ranger Rick ([EMAIL PROTECTED])
http://defiance.dyndns.org/ / http://radio.scenespot.org/
...if humanoids eat chicken, then obviously they'd eat their own
species. Otherwise they'd just be picking on the chickens. -- Kryten
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
