summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2011-November/004078.html
blob: f83c4b63e7c4490eead3ad9cbe99666f0bef2d7d (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
<!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%0A%09in%09basesystem-minimal%3F%20%28long%29&In-Reply-To=%3C20111109175034.GA21938%40mars-attacks.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="004079.html">
   <LINK REL="Next"  HREF="004080.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-sysadm] possibility to add a package	in	basesystem-minimal? (long)</H1>
    <B>nicolas vigier</B> 
    <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20possibility%20to%20add%20a%20package%0A%09in%09basesystem-minimal%3F%20%28long%29&In-Reply-To=%3C20111109175034.GA21938%40mars-attacks.org%3E"
       TITLE="[Mageia-sysadm] possibility to add a package	in	basesystem-minimal? (long)">boklm at mars-attacks.org
       </A><BR>
    <I>Wed Nov  9 18:50:34 CET 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="004079.html">[Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)
</A></li>
        <LI>Next message: <A HREF="004080.html">[Mageia-sysadm] possibility to add a package	in basesystem-minimal? (long)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#4078">[ date ]</a>
              <a href="thread.html#4078">[ thread ]</a>
              <a href="subject.html#4078">[ subject ]</a>
              <a href="author.html#4078">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Wed, 09 Nov 2011, Jerome Quelin wrote:

&gt;<i> 
</I>&gt;<i> to fix this problem, i can see the following solutions:
</I>&gt;<i> 
</I>&gt;<i> ** 1. patch our perl to provide a more recent EUMM
</I>&gt;<i> 
</I>&gt;<i> this is a no-go from my side. even the perl5 porters aren't updating the
</I>&gt;<i> bundled modules anymore [8], and i don't want to go down that road. so i
</I>&gt;<i> veto this solution with my perl-the-package maintainer hat.
</I>&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i> ** 2. update the buildrequires of all perl modules to require a more
</I>&gt;<i>       recent EUMM
</I>&gt;<i> 
</I>&gt;<i> this is a solution that's quite easy to do on my side: i just need to
</I>&gt;<i> update magpie to buildrequire a more recent EUMM if it's using a
</I>&gt;<i> makefile.PL and that no specific EUMM version is wanted. future perls
</I>&gt;<i> (5.16 and onward) will likely ship an updated EUMM, and therefore i'll
</I>&gt;<i> be able to remove this specific requirement in the spec files.  but i'm
</I>&gt;<i> wondering if that's not too much, given that it'll need ~1500 [9]
</I>&gt;<i> modules to be updated. and yes, the goal is to have a standard solution
</I>&gt;<i> for all modules, not only the problematic ones.
</I>
If it's planned to have in the futur other dependencies like this or rpm
macros to build perl packages, you can also create a new package
perl-rpmbuild with a require on EUMM (and other required packages to
build perl packages, if needed), with perl-rpmbuild added as buildrequire
on all perl packages.

&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i> ** 3. do nothing, and just deal with the problems manually
</I>&gt;<i> 
</I>&gt;<i> this is the solution i adopted till now. but i bump in more and more of
</I>&gt;<i> those exceptions, and this is a burden for me. mageia ships more than
</I>&gt;<i> 2500 perl modules, and usually i don't have to really dwelve in the
</I>&gt;<i> details of their updates. but each exception is taking some time from my
</I>&gt;<i> side to deal with, and i fear that the number of problems will just
</I>&gt;<i> continue to rise. so i'm wanting to quit using this &quot;solution&quot;, and find
</I>&gt;<i> a real one. almost as important, it means that finding a real solution
</I>&gt;<i> means we are following cpan evolution step by step, and i think it's a
</I>&gt;<i> Good Thing (tm).
</I>&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i> ** 4. update basesystem-minimal to ship perl-ExtUtils-MakeMaker
</I>&gt;<i> 
</I>&gt;<i> this way, no need to add a buildrequires for the modules. they all get
</I>&gt;<i> the new build tool, and therefore will generate the MYMETA files. 
</I>
Maybe adding this require to rpm-build instead of basesystem-minimal
would be enough.

</PRE>






<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="004079.html">[Mageia-sysadm] possibility to add a package in basesystem-minimal? (long)
</A></li>
	<LI>Next message: <A HREF="004080.html">[Mageia-sysadm] possibility to add a package	in basesystem-minimal? (long)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#4078">[ date ]</a>
              <a href="thread.html#4078">[ thread ]</a>
              <a href="subject.html#4078">[ subject ]</a>
              <a href="author.html#4078">[ 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>