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
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Package drop request: ruby-ParseTree
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20drop%20request%3A%20ruby-ParseTree&In-Reply-To=%3C20121210224245.GA17548%40shikamaru.fr%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="020715.html">
<LINK REL="Next" HREF="020732.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Package drop request: ruby-ParseTree</H1>
<B>Remy CLOUARD</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20drop%20request%3A%20ruby-ParseTree&In-Reply-To=%3C20121210224245.GA17548%40shikamaru.fr%3E"
TITLE="[Mageia-dev] Package drop request: ruby-ParseTree">shikamaru at shikamaru.fr
</A><BR>
<I>Mon Dec 10 23:42:45 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020715.html">[Mageia-dev] Package drop request: ruby-ParseTree
</A></li>
<LI>Next message: <A HREF="020732.html">[Mageia-dev] Package drop request: ruby-ParseTree
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20730">[ date ]</a>
<a href="thread.html#20730">[ thread ]</a>
<a href="subject.html#20730">[ subject ]</a>
<a href="author.html#20730">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Mon, Dec 10, 2012 at 03:55:05PM +0100, Guillaume Rousse wrote:
><i> Le 10/12/2012 14:01, Colin Guthrie a écrit :
</I>><i> >I see absolutely no problem with this and I don't consider this
</I>><i> >something that's done as a "side effect", rather it's a quite deliberate
</I>><i> >and concious mechanism to remove no longer supported packages from a
</I>><i> >users machine.
</I>><i> Shikamaru never asked about end user machines, but about mirrors.
</I>><i> Hence my point:
</I>><i> - if you just want to remove some files from the mirrors, ask an admin
</I>><i> - if you also want to remove old packages from end users machines,
</I>><i> first think twice about the expected result, then update
</I>><i> task-obsolete
</I>><i>
</I>><i> And on the more general interest of using obsolete tags, I'd rather
</I>><i> suggest to refrain from using them without a very good reason. In
</I>><i> ten years of contribution, I've never seen the mandriva bugzilla
</I>><i> drowned by bug reports about unsupported packages (the main argument
</I>><i> in support of the current 'thou shall obsoletes anything that is not
</I>><i> supported anymore' frenzy), whereas I've seen at least two recent
</I>><i> painful episodes in cauldron caused by careless packagers...
</I>Thanks, that pretty much clarify my intent indeed.
At first I didn’t even know task-obsolete existed in the first place so
I just followed the procedure Johnny explained. After understanding this
mechanism I don’t feel it was the right thing to do in this case.
First, because it’s a small ruby library that’s probably used by only a
handful of people. Second, this library is removed because it’s eol’d
upstream, but also because no other package use it. It seems to me that
it can safely be removed from the mirrors, but removing it from boxes
via task-obsolete seems a bit overkill to me, because that package would
have been orphaned because nothing requires it (unless someone
deliberately installed it, which I doubt)
I’m not yet sure about this but the way I see task-obsolete is that it
should only be used for end-applications, and even then I’m not
comfortable with silently removing things from people’s machines, I’d
rather use Conflicts instead.
Regards,
><i>
</I>><i> --
</I>><i> BOFH excuse #234:
</I>><i>
</I>><i> Someone is broadcasting pygmy packets and the router doesn't know
</I>><i> how to deal with them.
</I>--
Rémy CLOUARD
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020715.html">[Mageia-dev] Package drop request: ruby-ParseTree
</A></li>
<LI>Next message: <A HREF="020732.html">[Mageia-dev] Package drop request: ruby-ParseTree
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20730">[ date ]</a>
<a href="thread.html#20730">[ thread ]</a>
<a href="subject.html#20730">[ subject ]</a>
<a href="author.html#20730">[ 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>
|
