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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] new mgarepo version
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20new%20mgarepo%20version&In-Reply-To=%3C1310814824.3728.321.camel%40akroma.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006722.html">
<LINK REL="Next" HREF="006740.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] new mgarepo version</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20new%20mgarepo%20version&In-Reply-To=%3C1310814824.3728.321.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-dev] new mgarepo version">misc at zarb.org
</A><BR>
<I>Sat Jul 16 13:13:42 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006722.html">[Mageia-dev] new mgarepo version
</A></li>
<LI>Next message: <A HREF="006740.html">[Mageia-dev] new mgarepo version
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6734">[ date ]</a>
<a href="thread.html#6734">[ thread ]</a>
<a href="subject.html#6734">[ subject ]</a>
<a href="author.html#6734">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le samedi 16 juillet 2011 à 12:34 +0200, Samuel Verschelde a écrit :
><i> Le samedi 16 juillet 2011 12:20:22, Michael Scherer a écrit :
</I>><i>
</I>><i> > I am not keen on pushing our newer tool on update, since we plan to have
</I>><i> > our server using mageia, and so in the futur, if we push newer iurt,
</I>><i> > mgarepo, rpmlint, they may potentially disrupt build system. So by being
</I>><i> > clear and using backports, we would avoid such problem more easily.
</I>><i>
</I>><i> Except if you plan to use those newer version on the build system, in which
</I>><i> case sending to updates_testing to have them well tested then pushed to
</I>><i> updates would avoid having to install backports on the BS ?
</I>
We already have backports on the BS, and we will likely not be able to
avoid it. For example, transifex, while not being part of the BS per
se, is backported from cooker/cauldron. And it is planned to upgrade it
to next stable release, as asked by i18n team. There is no way that a
new tx would be pushed as update, that's too disruptive.
Moreover, I do not exclude the case that someone would deploy the same
build system as us ( let's say a company that provides custom version of
Mageia, a university that deploy custom build of software, whatever ),
and would prefer to not follow our upgrade path.
So I think the build system stuff should not have a exception for
updates.
Now, the problem arise also because mgarepo is used on both client side,
and server side.
On client side, it could likely fall as "needed to follow API changes",
at least for this version ( like would tx-client, or wesnoth ), even if
the problem is also the lack of web interface ( as this would avoid
requiring a new command line client ).
But on server side, the update reason doesn't apply.
So having a separate binary ( and/or tarball, while on it ) for the
server part, and make sure this one do not change much would be cleaner,
IMHO.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006722.html">[Mageia-dev] new mgarepo version
</A></li>
<LI>Next message: <A HREF="006740.html">[Mageia-dev] new mgarepo version
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6734">[ date ]</a>
<a href="thread.html#6734">[ thread ]</a>
<a href="subject.html#6734">[ subject ]</a>
<a href="author.html#6734">[ 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>
|
