blob: f1793f736bf614f0ccd973953f10fcc4a5c7356f (
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Packagers meeting
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Packagers%20meeting&In-Reply-To=%3C97614b37d99d96c1bf892219de2500fc.squirrel%40mail.rmail.be%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016902.html">
<LINK REL="Next" HREF="016905.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Packagers meeting</H1>
<B>AL13N</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Packagers%20meeting&In-Reply-To=%3C97614b37d99d96c1bf892219de2500fc.squirrel%40mail.rmail.be%3E"
TITLE="[Mageia-dev] Packagers meeting">alien at rmail.be
</A><BR>
<I>Wed Jun 27 13:13:54 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016902.html">[Mageia-dev] Packagers meeting
</A></li>
<LI>Next message: <A HREF="016905.html">[Mageia-dev] Packagers meeting
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16904">[ date ]</a>
<a href="thread.html#16904">[ thread ]</a>
<a href="subject.html#16904">[ subject ]</a>
<a href="author.html#16904">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>><i> 2012/6/27 Sander Lepik <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">sander.lepik at eesti.ee</A>>:
</I>>><i> I still don't understand where's the big problem if we enable release
</I>>><i> media for updates.
</I>>><i> It's not updated, so it shouldn't slow down updating too much. Hardware
</I>>><i> that can run DEs
</I>>><i> today should have no problems with release media enabled for updates. QA
</I>>><i> is proposing this
</I>>><i> solution again and again. Is this really that hard to change?
</I>
Don't forget that upgrades work similarly.
><i> The _simplest_ solution (conceptually speaking) would be to use a
</I>><i> condition which would enable release media for updates _if_ one or
</I>><i> more of the dependancies cannot be found in the updates media.
</I>><i> But I guess that it's not that simple in the code if it still has not
</I>><i> been considered otherwise than conceptually.
</I>
I think the simplest solution (code-wise) is to make sure that where-ever
you're looking for dependencies, is to have strict requires so that it
will always get the correct one.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016902.html">[Mageia-dev] Packagers meeting
</A></li>
<LI>Next message: <A HREF="016905.html">[Mageia-dev] Packagers meeting
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16904">[ date ]</a>
<a href="thread.html#16904">[ thread ]</a>
<a href="subject.html#16904">[ subject ]</a>
<a href="author.html#16904">[ 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>
|
