Kyle, the big difference between my proposal and your proposal is that
my proposal puts the burden of keeping things straight on the maintainer
of the package providing the libraries, and your proposal puts the
burden of keeping things straight on the maintainers of other packages.
Under your
Under your system, let's say I introduce foo-3.0.0 which is not
backwards
compatible. Now all of the other developers need to revise their
packages
immediately, because their packages were saying
Depends: foo (= 2.0.0)
but now they need to say
Depends: foo (= 2.0.0 3.0.0)
I thought it might be worth sketching a possible roadmap to full shared
libraries support for fink.
Phase 1: Convert some of the shared libraries packages to the
foo/foo-shlibs system. Be sure to include all packages where the major
version number is likely to change soon, or has
I've just updated the system-tetex package, which I try to do very
infrequently. One of the new features is a much more robust
pre-install script.
I haven't been able to find a solution to the following problem: some
users will need to do a bit of disk housekeeping (removing obsolete
files by
