blob: 33a5394bb79a2a5d02a63e4dfbee9a9a73f8772f (
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
94
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Package removal proposal
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20removal%20proposal&In-Reply-To=%3C20120826204706.GS30221%40virgo.nanardon.zarb.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="018309.html">
<LINK REL="Next" HREF="018314.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Package removal proposal</H1>
<B>Olivier Thauvin</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20removal%20proposal&In-Reply-To=%3C20120826204706.GS30221%40virgo.nanardon.zarb.org%3E"
TITLE="[Mageia-dev] Package removal proposal">nanardon at nanardon.zarb.org
</A><BR>
<I>Sun Aug 26 22:47:06 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018309.html">[Mageia-dev] Package removal proposal
</A></li>
<LI>Next message: <A HREF="018314.html">[Mageia-dev] Package removal proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18312">[ date ]</a>
<a href="thread.html#18312">[ thread ]</a>
<a href="subject.html#18312">[ subject ]</a>
<a href="author.html#18312">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>* Colin Guthrie (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>) wrote:
><i> In my opinion we should run a tight ship. If users want to use something
</I>><i> we no longer ship, then they still have several choices:
</I>><i> 1. Don't install task-obsolete and add it to their skip.list.
</I>
As obsoletes are automatically promote, there is no way to keep a package
except adding it to skip.list.
><i> 3. Package it and become a contributor (assuming the reason for
</I>><i> dropping the package was due to a lack of maintainer rather than a
</I>><i> specific desire/reason (i.e. legal))
</I>
Sys admin work is not to make package.
><i>
</I>><i> For all of these options the user is both informed and can make a very
</I>><i> clear, concious choice about how they want to proceed and know the
</I>><i> consequences of doing so.
</I>
This system silently remove packages. I am pretty sure a lot of people
will wonder why some need libraries get removed from their system at
each update...
--
Olivier Thauvin
CNRS - LATMOS
♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: </pipermail/mageia-dev/attachments/20120826/0b140350/attachment.asc>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018309.html">[Mageia-dev] Package removal proposal
</A></li>
<LI>Next message: <A HREF="018314.html">[Mageia-dev] Package removal proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18312">[ date ]</a>
<a href="thread.html#18312">[ thread ]</a>
<a href="subject.html#18312">[ subject ]</a>
<a href="author.html#18312">[ 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>
|