summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005931.html
blob: 1489a7a77d3db4e64a0651c893fad19022645329 (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
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Minimal patching vs. fixing the whole Universe
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Minimal%20patching%20vs.%20fixing%20the%20whole%20Universe&In-Reply-To=%3CBANLkTi%3DvR%2BQmyFFHDxy9WoLZ2DUnRmY79w%40mail.gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="005930.html">
   <LINK REL="Next"  HREF="005932.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Minimal patching vs. fixing the whole Universe</H1>
    <B>John Balcaen</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Minimal%20patching%20vs.%20fixing%20the%20whole%20Universe&In-Reply-To=%3CBANLkTi%3DvR%2BQmyFFHDxy9WoLZ2DUnRmY79w%40mail.gmail.com%3E"
       TITLE="[Mageia-dev] Minimal patching vs. fixing the whole Universe">mikala at mageia.org
       </A><BR>
    <I>Wed Jun 22 22:58:36 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="005930.html">[Mageia-dev] Minimal patching vs. fixing the whole Universe
</A></li>
        <LI>Next message: <A HREF="005932.html">[Mageia-dev] Minimal patching vs. fixing the whole Universe
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5931">[ date ]</a>
              <a href="thread.html#5931">[ thread ]</a>
              <a href="subject.html#5931">[ subject ]</a>
              <a href="author.html#5931">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>2011/6/22 Radu-Cristian FOTESCU &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">beranger5ca at yahoo.ca</A>&gt;:
&gt;<i> I'm known to be grumpy and difficult, but I also believe in simplicity as a policy, therefore I'd like to ask you something.
</I>&gt;<i>
</I>&gt;<i> By no means I want to question Ahmad's judgment, however I strongly disagree with him on one point. As a _principle_. Otherwise, it's a tiny punctual question, but I'd like to know Mageia's patching _policy_.
</I>&gt;<i>
</I>&gt;<i> See comments 50 and downwards:
</I>&gt;<i>
</I>&gt;<i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=1659#c50">https://bugs.mageia.org/show_bug.cgi?id=1659#c50</A>
</I>&gt;<i>
</I>&gt;<i> calibre-python2-env-fix.patch replaces
</I>&gt;<i> '/usr/bin/env python2'
</I>&gt;<i> with
</I>&gt;<i> '/usr/bin/env python'
</I>&gt;<i>
</I>&gt;<i> The calibre developer has used '/usr/bin/env python' for ages, but relatively recently he has decided to switch to '/usr/bin/env python2' for fear that some distros would use Python 3 by default.
</I>&gt;<i>
</I>&gt;<i> Ahmad insists that '/usr/bin/python' should be used in Mageia.
</I>&gt;<i>
</I>&gt;<i> As long as '/usr/bin/env python' _works_, I see no point in trying to rewrite other people's work.
</I>&gt;<i>
</I>&gt;<i> I would say that the general principle should be to apply a _minimal_ patching, not to try to rewrite the work of the developers of hundreds of packages!
</I>&gt;<i>
</I>&gt;<i> A distro's job is not to judge the work of the _upstream_ developers as long as this is not a real bug.
</I>&gt;<i>
</I>&gt;<i> &quot;Should&quot; Mageia try to &quot;fix&quot; something that is not actually broken? There might be hundreds of packages with thousands and thousands of questionable decisions taken by the upstream developers -- however, why fixing something that works?
</I>&gt;<i>
</I>&gt;<i> You see, I hate conflicts (although I seem to be a maestro in generating them), but I also need simplicity and clear policies. Also, policies that can be applied. &quot;Perfect&quot; policies that would require the revision of hundreds of packages that actually work are not my cup of tea.
</I>&gt;<i>
</I>&gt;<i> Of course, I am _not_ a Mageia packager and this is not &quot;my&quot; package, but I'd like to know Mageia's policy wrt building packages. Normally, patches are not meant to optimize but to fix breakages. If the packagers are compelled to &quot;improve&quot; upstream's work, this can prove to be catastrophic in complex cases.
</I>
We don't have any python2 symlink or binary on mageia.
</PRE>
































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="005930.html">[Mageia-dev] Minimal patching vs. fixing the whole Universe
</A></li>
	<LI>Next message: <A HREF="005932.html">[Mageia-dev] Minimal patching vs. fixing the whole Universe
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5931">[ date ]</a>
              <a href="thread.html#5931">[ thread ]</a>
              <a href="subject.html#5931">[ subject ]</a>
              <a href="author.html#5931">[ 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>