On Tue, Aug 21, 2001 at 02:18:52PM -0700, Christopher Maujean wrote:
> Can someone explain the debian policy on what version of a package gets
> includeed in the relase? And, How would I go about upgrading my package (sendmail
> say) to a newer version than the one that came in the release (potato), yet
> retain debian compatability (configs etc)?
>
(Sorry for the delayed response)
Debian has a rather large policy manual, that explains A LOT.
apt-get install debian-policy, IIRC
OTOH, I think it's a good practice to know how to /fix/ things in a way
that jives with the system. In the case of Debian, that means
understanding how to make .debs, which is far beyond the scope of this
email ;P
If you want to run new code and maintain binary compatability, you could
also download the src-deb, and build it on a potato system. I had to do
that with the ssh package in unstable once (ssl version mismatch). This
might not always work, however, as it may require new dependencies (and
meeting those dependencies could lead you into a LONG trail of
dependencies). I don't think this would be a problem in sendmail's
case, though. You can also tweak the dependency info if you know what
you're doing won't cause a problem. Basically, most of the work is done
for you, you just have to make sure it's right.
Of course, this is less of a problem on systems that actually install
from source, like OpenBSD. (Sorry, I just HAD to say that, hehehe)
--
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
