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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20possibility%20to%20add%20a%20package%09in%0A%20basesystem-minimal%3F%20%28long%29&In-Reply-To=%3C4EBAC968.7010709%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="004078.html">
<LINK REL="Next" HREF="004081.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)</H1>
<B>Thomas Backlund</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20possibility%20to%20add%20a%20package%09in%0A%20basesystem-minimal%3F%20%28long%29&In-Reply-To=%3C4EBAC968.7010709%40mageia.org%3E"
TITLE="[Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)">tmb at mageia.org
</A><BR>
<I>Wed Nov 9 19:41:44 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="004078.html">[Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)
</A></li>
<LI>Next message: <A HREF="004081.html">[Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4080">[ date ]</a>
<a href="thread.html#4080">[ thread ]</a>
<a href="subject.html#4080">[ subject ]</a>
<a href="author.html#4080">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>nicolas vigier skrev 9.11.2011 19:50:
><i> On Wed, 09 Nov 2011, Jerome Quelin wrote:
</I>><i>
</I>>><i>
</I>>><i> to fix this problem, i can see the following solutions:
</I>>><i>
</I>>><i> ** 1. patch our perl to provide a more recent EUMM
</I>>><i>
</I>>><i> this is a no-go from my side. even the perl5 porters aren't updating the
</I>>><i> bundled modules anymore [8], and i don't want to go down that road. so i
</I>>><i> veto this solution with my perl-the-package maintainer hat.
</I>>><i>
</I>>><i>
</I>>><i> ** 2. update the buildrequires of all perl modules to require a more
</I>>><i> recent EUMM
</I>>><i>
</I>>><i> this is a solution that's quite easy to do on my side: i just need to
</I>>><i> update magpie to buildrequire a more recent EUMM if it's using a
</I>>><i> makefile.PL and that no specific EUMM version is wanted. future perls
</I>>><i> (5.16 and onward) will likely ship an updated EUMM, and therefore i'll
</I>>><i> be able to remove this specific requirement in the spec files. but i'm
</I>>><i> wondering if that's not too much, given that it'll need ~1500 [9]
</I>>><i> modules to be updated. and yes, the goal is to have a standard solution
</I>>><i> for all modules, not only the problematic ones.
</I>><i>
</I>><i> If it's planned to have in the futur other dependencies like this or rpm
</I>><i> macros to build perl packages, you can also create a new package
</I>><i> perl-rpmbuild with a require on EUMM (and other required packages to
</I>><i> build perl packages, if needed), with perl-rpmbuild added as buildrequire
</I>><i> on all perl packages.
</I>><i>
</I>
Well, having to change only one package instead of all would probably
be nicer if possible.
>><i>
</I>>><i>
</I>>><i> ** 3. do nothing, and just deal with the problems manually
</I>>><i>
</I>>><i> this is the solution i adopted till now. but i bump in more and more of
</I>>><i> those exceptions, and this is a burden for me. mageia ships more than
</I>>><i> 2500 perl modules, and usually i don't have to really dwelve in the
</I>>><i> details of their updates. but each exception is taking some time from my
</I>>><i> side to deal with, and i fear that the number of problems will just
</I>>><i> continue to rise. so i'm wanting to quit using this "solution", and find
</I>>><i> a real one. almost as important, it means that finding a real solution
</I>>><i> means we are following cpan evolution step by step, and i think it's a
</I>>><i> Good Thing (tm).
</I>>><i>
</I>>><i>
</I>>><i> ** 4. update basesystem-minimal to ship perl-ExtUtils-MakeMaker
</I>>><i>
</I>>><i> this way, no need to add a buildrequires for the modules. they all get
</I>>><i> the new build tool, and therefore will generate the MYMETA files.
</I>><i>
</I>><i> Maybe adding this require to rpm-build instead of basesystem-minimal
</I>><i> would be enough.
</I>><i>
</I>
That would make it more in line for only building rpms, or add it to
iurt if we want to ensure it "only" the bs ...
Of course we probably will get complaints on "bloating" rpmbuild or iurt
then :)
Or do we have to ensure it ends up on all systems that are used for perl
development? should it then be pulled in by some perl-*
I see basesystem-minimal pulls only:
perl-File-Sync
perl-MDK-Common
perl-WWW-Curl
perl-base
do we have some perl-* package that is required for all perl developers,
but that is not some of the above?
--
Thomas
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="004078.html">[Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)
</A></li>
<LI>Next message: <A HREF="004081.html">[Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4080">[ date ]</a>
<a href="thread.html#4080">[ thread ]</a>
<a href="subject.html#4080">[ subject ]</a>
<a href="author.html#4080">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|
