Re: XFree86 3.3.2.3a-8pre9v6 at master.debian.org/~branden/xfree86
- To: debian-devel@lists.debian.org
- Subject: Re: XFree86 3.3.2.3a-8pre9v6 at master.debian.org/~branden/xfree86
- From: A.J.Gray@durham.ac.uk
- Date: Mon, 1 Feb 1999 23:42:37 GMT
- Message-id: <[🔎] 6481.199902021003@altair>
- In-reply-to: <Pine.LNX.3.96.990129144447.9413I-100000@cantor.unex.es>; from Santiago Vila on Fri, Jan 29, 1999 at 02:58:45PM +0100
- References: <19990128062357.A2154@ecn.purdue.edu> <Pine.LNX.3.96.990129144447.9413I-100000@cantor.unex.es>
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, Jan 29, 1999 at 02:58:45PM +0100, Santiago Vila wrote:
> Branden Robinson:
> > I don't know yet exactly how the new font and static library packages
> > will be handled. I want to build developer consensus on a solution.
>
> I have one possible solution here:
<snip - the message, that is - I won't comment on the solution...>
Not a solution, but an observation as a fairly ordinary user who recently
upgraded hamm->slink, using dselect/apt. The name change didn't cause any
problems ONCE I had worked out what was going on. As far as I am concerned, a
good release note (perhaps mentioned in an xbase-postinst) and BIG warnings in
the Description fields for the xfonts- packages would have been sufficient to
make the upgrade perfectly smooth in practice. Not technically perfect,
perhaps, but enough to keep this dumb user happy!
Andrew
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQCVAwUBNrY76MGi+yVEBdQpAQEIbAP+PPbLSufidp9BMoPOMh3rMWia1e+UlNgB
2EivJKWMQNM30wjvR1EIfrd+YSiFc0N4XqFQDjspWbM0HJ3vFMFsBDEyBpzg7cq5
6zNx//rxYznGLrW/yF2kFF8MPJKWisYGEIbdwFZlVBAB4epICpMe4dqrPVRGMkma
EszNciFDwB0=
=XuVe
-----END PGP SIGNATURE-----
Reply to: