From: "D. Wollmann" <converter@dalnet-perl.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] random perl ebuilds (5.6.1 -> 5.8.0 -> 5.6.1)?
Date: Mon, 30 Dec 2002 02:21:07 -0600 [thread overview]
Message-ID: <200212300221.26415.converter@dalnet-perl.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Why do I find my gentoo system upgrading from perl 5.6.1 to perl 5.8.0 (a good
thing, since 5.8.0 includes patches for many, many bad bugs), then a couple
of days later wanting to downgrade back to perl 5.6.1?
Please, if you're going to make version changes of this magnitude, include an
explanation somewhere, preferably in the ChangeLog. The absence of an
explanation does not inspire confidence. Something as simple as "perl 5.8.0
had problems, downgrading to perl 5.6.1" would be more than enough.
Thanks, and keep up the good work!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+EAIDm+D7kzTIiiERAlk1AJ92JwZdByd4ZOY2LSQtobadWg7zVACgvlwF
BMCLe6SN+8EV/Nyqsfx2Q2E=
=lj+j
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2002-12-30 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 8:21 D. Wollmann [this message]
2002-12-30 9:29 ` [gentoo-dev] random perl ebuilds (5.6.1 -> 5.8.0 -> 5.6.1)? Michael Cummings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212300221.26415.converter@dalnet-perl.org \
--to=converter@dalnet-perl.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox