Re: A real case.
[Sorry for jumping in...]
On Thu, 25 Sep 1997, Fabrizio Polacco wrote:
> When an Author releases an upgrade version of a library,
> after some time of testing, and declares it as "stable" why should other
> Authors wait for debian to release "unstable" as "stable" just to use
> the library?
The other Authors have a few options:
1) They link their program statically.
2) They include the new library in the program.deb package.
(Yes, I know those are not optimal).
3) They package the new library also, mark it as non-Debian release,
and use a non-number version, something like libfoo_jra.1.deb, where
jra are Joe Random Author initials. Of course, program.deb will have to
depend on libfoo (= jra.1).
It's nothing different for .rpm, is it?
What if JRA wants to release a libc6-based program for Red Hat?
Currently Red Hat doesn't offer an stable libc6-based system, so
if a user wants to use that program, he will have to find a way to
upgrade his Red Hat 4.2 system to a libc6-based system.
So if JRA wants that Debian 1.3.1 users run his program, he will have to
use libraries already in Debian 1.3.1. Else he will have to provide his
own upgrade path, and warn the users they are leaving "terra cognita"
(possibly with a big "here be dragons" sign).
--
Enrique Zanardi ezanardi@ull.es
Dpto. Fisica Fundamental y Experimental Univ. de La Laguna
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: