blob: 38432468a32623712b32359d3003906978d3939d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Removal of sun java
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Removal%20of%20sun%20java&In-Reply-To=%3C4F75BD22.9050904%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="013725.html">
<LINK REL="Next" HREF="013737.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Removal of sun java</H1>
<B>Guillaume Rousse</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Removal%20of%20sun%20java&In-Reply-To=%3C4F75BD22.9050904%40gmail.com%3E"
TITLE="[Mageia-dev] Removal of sun java">guillomovitch at gmail.com
</A><BR>
<I>Fri Mar 30 16:03:14 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="013725.html">[Mageia-dev] Removal of sun java
</A></li>
<LI>Next message: <A HREF="013737.html">[Mageia-dev] Removal of sun java
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13728">[ date ]</a>
<a href="thread.html#13728">[ thread ]</a>
<a href="subject.html#13728">[ subject ]</a>
<a href="author.html#13728">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 30/03/2012 15:25, Christian Lohmaier a écrit :
><i> If that is not reading: Don't push the security updates to the users,
</I>><i> let the user take care of that manually, then what else?
</I>That just means 'give the end user everything he needs to take a
decision (advice, notification, packages, popup, whatever) but let him
take this decision about this specific issue himself'.
Let's try to move toward a consensus...
Mixing removing of sun jdk with updating another jdk for security seems
an unfair bundle, as you can't have one without another.
Issuing a specific sun jdk security update package, containing only a
README.urpmi file and a shell script inciting the user to read this file
eventually, would be a fair compromise for me. And can be considered as
a standard practice for semi-automatically removing
very-dangerous-packages-we-cannot-afford-to-let-installed-anywhere-otherwise-the-apocalypse-will-happen.
--
BOFH excuse #8:
static buildup
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="013725.html">[Mageia-dev] Removal of sun java
</A></li>
<LI>Next message: <A HREF="013737.html">[Mageia-dev] Removal of sun java
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13728">[ date ]</a>
<a href="thread.html#13728">[ thread ]</a>
<a href="subject.html#13728">[ subject ]</a>
<a href="author.html#13728">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
