summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-August/018309.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-August/018309.html')
-rw-r--r--zarb-ml/mageia-dev/2012-August/018309.html103
1 files changed, 103 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-August/018309.html b/zarb-ml/mageia-dev/2012-August/018309.html
new file mode 100644
index 000000000..b6d42c8e3
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-August/018309.html
@@ -0,0 +1,103 @@
+<!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=%3C503A33B2.5050402%40eesti.ee%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="018308.html">
+ <LINK REL="Next" HREF="018312.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Package removal proposal</H1>
+ <B>Sander Lepik</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20removal%20proposal&In-Reply-To=%3C503A33B2.5050402%40eesti.ee%3E"
+ TITLE="[Mageia-dev] Package removal proposal">sander.lepik at eesti.ee
+ </A><BR>
+ <I>Sun Aug 26 16:33:22 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="018308.html">[Mageia-dev] Package removal proposal
+</A></li>
+ <LI>Next message: <A HREF="018312.html">[Mageia-dev] Package removal proposal
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#18309">[ date ]</a>
+ <a href="thread.html#18309">[ thread ]</a>
+ <a href="subject.html#18309">[ subject ]</a>
+ <a href="author.html#18309">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>
+Sander
+
+26.08.2012 17:15, Colin Guthrie kirjutas:
+&gt;<i> 'Twas brillig, and Johnny A. Solbu at 25/08/12 02:42 did gyre and gimble:
+</I>&gt;&gt;<i> On Saturday 25 August 2012 02:33, Olivier Thauvin wrote:
+</I>&gt;&gt;&gt;<i> For me obsolete should be reserved for replacements or rename, nothing
+</I>&gt;&gt;&gt;<i> more.
+</I>&gt;&gt;<i> I agree on this.
+</I>&gt;<i> So in two years time, we add a new package with the same filename as one
+</I>&gt;<i> of these old package, we may get some very strange edge cases on package
+</I>&gt;<i> upgrades/installer because keeping these old, no longer shipped packages
+</I>&gt;<i> installed is still &quot;supported&quot; (of course this could happen even if the
+</I>&gt;<i> old package were obsoleted properly, due to package install order on
+</I>&gt;<i> upgrades)
+</I>&gt;<i>
+</I>&gt;<i> What about when there are security issues in the old package? Do we just
+</I>&gt;<i> drop it and then wash our hands of the whole affair and don't give a
+</I>&gt;<i> crap when a user's system is completely compromised?
+</I>&gt;<i>
+</I>&gt;<i> In my opinion we should run a tight ship. If users want to use something
+</I>&gt;<i> we no longer ship, then they still have several choices:
+</I>&gt;<i> 1. Don't install task-obsolete and add it to their skip.list.
+</I>&gt;<i> 2. Do a local compile+install into /usr/local of the software in question
+</I>&gt;<i> 3. Package it and become a contributor (assuming the reason for
+</I>&gt;<i> dropping the package was due to a lack of maintainer rather than a
+</I>&gt;<i> specific desire/reason (i.e. legal))
+</I>&gt;<i>
+</I>&gt;<i> For all of these options the user is both informed and can make a very
+</I>&gt;<i> clear, concious choice about how they want to proceed and know the
+</I>&gt;<i> consequences of doing so.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Obsoletes in packages which genuinely replace the old one seem
+</I>&gt;<i> reasonable and uncontroversial.
+</I>&gt;<i>
+</I>&gt;<i> Col
+</I>&gt;<i>
+</I>What about new feature. Some txt file (containing obsoleted package per line and probably
+can be signed somehow) in the mirrors that can be updated by sysadmins. During update urpmi
+will check this file and will compare with local file where user has marked what (s)he wants
+to do with those packages (&lt;obsoleted package&gt; &lt;status: keep/remove&gt; per line). If urpmi
+finds package that hasn't been listed in local file it will ask the user what to do with it
++ will show warning that all possible security problems are not our problem anymore.
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="018308.html">[Mageia-dev] Package removal proposal
+</A></li>
+ <LI>Next message: <A HREF="018312.html">[Mageia-dev] Package removal proposal
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#18309">[ date ]</a>
+ <a href="thread.html#18309">[ thread ]</a>
+ <a href="subject.html#18309">[ subject ]</a>
+ <a href="author.html#18309">[ 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>