Re: post-release package update policy
firstname.lastname@example.org (Dale Scheetz) wrote on 26.10.95 in <Pine.LNX.3.91.951026144546.1236A-100000@localhost>:
> On 26 Oct 1995, Kai Henningsen wrote:
> > email@example.com (Dale Scheetz) wrote on 25.10.95 in
> > <9510251914.AA12174@symnet.net>:
> > [...]
> > > Product is. While trying to build a system, dpkg changed enough to loose
> > > it's old database (rather than provide a conversion) and "forgot" that
> > > it had installed the base package. When I went to remidy that problem,
> > > the only
> > [...]
> > That's a bad experience all right, but I just don't see how having a non-
> > changing release would have avoided it.
> Well, I do! It would have given me the opportunity to fall back to the
> "release" package anytime I install an updated package that, for one
> reason or another, fails to opperate to my liking.
Why do you think this wouldn't have hapened with the "release" package?
Why could you not go back to whatever package you had installed
Sorry, but I don't think your problem had anything at all to do with
whatever is labelled a release.