Gentoo Archives: gentoo-dev

From: Riyad Kalla <rsk@×××××××××.edu>
To: 'Paul de Vrieze' <gentoo-user@××××××××.net>, gentoo-dev@g.o
Subject: RE: [gentoo-dev] Re: [gentoo-security] Update to perl 5.8 disables most perl dependent programms
Date: Sun, 12 Jan 2003 16:01:26
Message-Id: 000001c2ba53$20526d80$0200000a@rsk
In Reply to: [gentoo-dev] Re: [gentoo-security] Update to perl 5.8 disables most perl dependent programms by Paul de Vrieze
1 I agree with paul. This is just good practice. It is also stated in the
2 digests as well about the perl situation, so its not like the
3 information wasn't available.
4
5 -----Original Message-----
6 From: Paul de Vrieze [mailto:gentoo-user@××××××××.net]
7 Sent: Sunday, January 12, 2003 7:12 AM
8 To: gentoo-dev@g.o
9 Subject: [gentoo-dev] Re: [gentoo-security] Update to perl 5.8 disables
10 most perl dependent programms
11
12
13 On Sunday 12 January 2003 03:58, Alexander Holler wrote:
14 > Hi,
15 >
16 > I would find it good if such major critical updates could be announced
17 some
18 > time before they are released. At my site this update has at least
19 disabled
20 > irssi and amavis.
21 > In the case of amavis all incoming e-mail is has been rejected.
22 >
23
24 At such a site do two things:
25 - Review all, I mean ALL, updates and be critical about what is being
26 updated.
27 With essential systems one might even choose not to update unless
28 there is a
29 specific reason to do so.
30 - Follow at least the gentoo-dev mailing list. Major updates come by
31 some time
32 before they come out of testing. Most times indicating problems and
33 solutions. That way difficult updates such as: perl libpng gcc-3.2
34 xft2 etc.
35 can be identified. For me I wait with such updates for at least a
36 couple of
37 weeks after they have been released. After that I will try them first
38 on one
39 machine, before installing it on all.
40
41 Paul
42
43 --
44 Paul de Vrieze
45 Researcher
46 Mail: pauldv@××××××.nl
47 Homepage: http://www.devrieze.net
48
49
50 --
51 gentoo-dev@g.o mailing list