summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005790.html
blob: 9e44802a06b9b8e5683dc80f5fb6b099fe3978a6 (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
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Question about backports: calibre (bug 1659)
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Question%20about%20backports%3A%20calibre%20%28bug%201659%29&In-Reply-To=%3C4DFA75AA.9010502%40laposte.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="005753.html">
   <LINK REL="Next"  HREF="005794.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Question about backports: calibre (bug 1659)</H1>
    <B>andre999</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Question%20about%20backports%3A%20calibre%20%28bug%201659%29&In-Reply-To=%3C4DFA75AA.9010502%40laposte.net%3E"
       TITLE="[Mageia-dev] Question about backports: calibre (bug 1659)">andr55 at laposte.net
       </A><BR>
    <I>Thu Jun 16 23:29:14 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="005753.html">[Mageia-dev] Question about backports: calibre (bug 1659)
</A></li>
        <LI>Next message: <A HREF="005794.html">[Mageia-dev] Question about backports: calibre (bug 1659)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5790">[ date ]</a>
              <a href="thread.html#5790">[ thread ]</a>
              <a href="subject.html#5790">[ subject ]</a>
              <a href="author.html#5790">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Radu-Cristian FOTESCU a &#233;crit :
&gt;<i>
</I>&gt;&gt;<i> From: andre999&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>&gt;
</I>&gt;&gt;<i>
</I>&gt;<i> [...]
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> ...
</I>&gt;&gt;<i> Considering your concern for the application, maybe you would
</I>&gt;&gt;<i> like to package it for Mageia.  You could ensure that it is always up to date, and that it
</I>&gt;&gt;<i> works properly, and is properly supported.  (The packager is a key player in support.) Just
</I>&gt;&gt;<i> because it is called a backport doesn't mean that it won't work. The packager mentoring
</I>&gt;&gt;<i> program will help you get started :)
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> -- Andr&#233;
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i> Well, first of all, I never liked the _concept_ of backports. Too many repositories, too complex
</I>&gt;<i> tree already. One of the reasons I wasn't very fond of Mandriva (the other reason being the
</I>&gt;<i> IaOra theme(s).)
</I>
As Stormi suggested, you could consider backports as &quot;feature updates&quot;.  (Whether or not the 
repository names change.)
There is a certain logic for having separate backport repositories.
It is normal to put more focus on security updates and bug fixes, than introducing new features.
The former could also be considered release blockers, but never backports.
So QA focuses on security updates and bug fixes.
Also, Mandriva provided corporate support for the former, but not backports.  Of course this 
concept doesn't apply to a volonteer community distro such as Mageia.
Mageia policy is inherited from Mandriva, but is evidently subject to changes.
In terms of support, the nature of support by Mageia is yet to be defined, but it is starting to be 
discussed.

&gt;<i> From the NON-rolling distros, Fedora is arguably the only one who tries to bring newer versions
</I>&gt;<i> of a number of applications throughout its 12+1 months lifecycle. w/o using backports. My
</I>&gt;<i> opinion is that, as long as system libraries are _not_ upgraded, many other packages
</I>&gt;<i> (applications!) should be updated as appropriate. Otherwise, the result would be that Windows
</I>&gt;<i> users would have more freedom and ease in decided what version of the [multi-platform
</I>&gt;<i> open-source] applications to use than Linux users! (Except, of course, the users of
</I>&gt;<i> rolling-release distros, and except for users of unstable/rawhide/cooker/cauldron...)
</I>&gt;<i>
</I>&gt;<i> I know, I should probably be using Fedora as long as _some_ of their principles suit my views
</I>&gt;<i> much more than Mageia does or than Mandriva did. However, Fedora lacks something like Mandriva
</I>&gt;<i> Control Center, and yum is millions of times slower than urpmi, therefore...
</I>
I appreciate the same strengths inherited by Mageia.

&gt;<i> Not to mention that most of the best people Mandriva had are now with Mageia, which makes this
</I>&gt;<i> distro hard to ignore... (Je crois qu'on appelle cela zugzwang...)
</I>
I agree totally.  Mageia is the best of the old Mandriva.

So what I propose is that you seriously consider packaging your application for Mageia.
We find a mentor for you to apprentice with, to familiarise you with the process.
In choosing a mentor, it would help to find someone in the same time zone.
You're in Canada ?  What time zone ?
(I'd offer to mentor you myself, being also in Canada, but I'm not yet a full packager.)
When I started, I was able to package my favorite application to start with, hopefully you can do 
the same, if it's not too complicated.  (Since you indicate that it doesn't have dependancies 
to/from other packages, I suspect that it would be relatively straight-forward.)
Once you have started packaging, you have a better chance to influence Mageia policy, if you still 
think that it should be changed.
But in any case you would be able to ensure that your package is available on Mageia, and is always 
up to date.
And of course, ensure that it works properly.

So, isn't it worth a try ? :)
&gt;<i>
</I>&gt;<i> R-C
</I>
-- 
Andr&#233;
</PRE>





































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="005753.html">[Mageia-dev] Question about backports: calibre (bug 1659)
</A></li>
	<LI>Next message: <A HREF="005794.html">[Mageia-dev] Question about backports: calibre (bug 1659)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5790">[ date ]</a>
              <a href="thread.html#5790">[ thread ]</a>
              <a href="subject.html#5790">[ subject ]</a>
              <a href="author.html#5790">[ 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>