summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-July/017656.html
blob: 81a5913cbd9dab9a2735c8e423ac292daaef0742 (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] %{_unitdir} after /usr move
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%25%7B_unitdir%7D%20after%20/usr%20move&In-Reply-To=%3C20120724143556.GW21938%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="017655.html">
   <LINK REL="Next"  HREF="017657.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] %{_unitdir} after /usr move</H1>
    <B>nicolas vigier</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%25%7B_unitdir%7D%20after%20/usr%20move&In-Reply-To=%3C20120724143556.GW21938%40mars-attacks.org%3E"
       TITLE="[Mageia-dev] %{_unitdir} after /usr move">boklm at mars-attacks.org
       </A><BR>
    <I>Tue Jul 24 16:35:56 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="017655.html">[Mageia-dev] %{_unitdir} after /usr move
</A></li>
        <LI>Next message: <A HREF="017657.html">[Mageia-dev] %{_unitdir} after /usr move
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#17656">[ date ]</a>
              <a href="thread.html#17656">[ thread ]</a>
              <a href="subject.html#17656">[ subject ]</a>
              <a href="author.html#17656">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Tue, 24 Jul 2012, Colin Guthrie wrote:

&gt;<i> 'Twas brillig, and Olav Vitters at 24/07/12 15:11 did gyre and gimble:
</I>&gt;<i> &gt; $ rpm -E '%{_unitdir}'
</I>&gt;<i> &gt; /lib/systemd/system
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; This should show:
</I>&gt;<i> &gt; /usr/lib/systemd/system
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; I see that it is defined in two places:
</I>&gt;<i> &gt; 1. /etc/rpm/macros.d/20build.macros: %_unitdir /lib/systemd/system
</I>&gt;<i> &gt; 2. /usr/lib/rpm/macros.systemd: %_unitdir /usr/lib/systemd/system
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; The latter obviously provides the right setting. But I guess due to
</I>&gt;<i> &gt; ordering and so on it picks up the setting from 20build.macros.
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; This is preventing me to package NetworkManager properly (I prefer
</I>&gt;<i> &gt; relying on %{_unitdir} to give me the location, so the spec still works
</I>&gt;<i> &gt; on Mageia 2).
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; Could someone fix this?
</I>&gt;<i> 
</I>&gt;<i> Yeah this was on my to-fix list.
</I>&gt;<i> 
</I>&gt;<i> As far as I'm aware the file in /usr/lib/rpm/macros.systemd will not be
</I>&gt;<i> looked at at all anyway as it's not in any kind of magical .d folder.
</I>&gt;<i> 
</I>&gt;<i> I would like to see the following changes:
</I>&gt;<i> 
</I>&gt;<i> 1) We define a /usr/lib/rpm/macros.d/ folder.
</I>&gt;<i> 2) Any packages shipping file in the /etc/ folder should change and use
</I>&gt;<i> /usr/lib instead (/etc should be for admin overrides, NOT for general
</I>&gt;<i> packaging).
</I>&gt;<i> 3) We include the systemd macos in the /usr/lib/rpm/macos.d/ folder.
</I>
This looks like a good idea.

&gt;<i> 4) Any files shipping systemd units require systemd-devel to ensure they
</I>&gt;<i> have the macro.
</I>&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i> While steps 1-3 are probably OK (just need work) I'm not sure if
</I>&gt;<i> requiring systemd-devel is overkill when all they need is a small part
</I>&gt;<i> of it. I could potentially create a systemd-unit-devel package which
</I>&gt;<i> only contained the neccesary stuff which would be lighter on the
</I>&gt;<i> requirements front but I'm also against too much fragmentation here, so
</I>&gt;<i> I'd be tempted to just say &quot;require systemd-devel&quot; and sod the
</I>&gt;<i> not-strictly-necessary stuff it might end up pulling in.
</I>
Are you talking about buildrequires ?

</PRE>




































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="017655.html">[Mageia-dev] %{_unitdir} after /usr move
</A></li>
	<LI>Next message: <A HREF="017657.html">[Mageia-dev] %{_unitdir} after /usr move
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#17656">[ date ]</a>
              <a href="thread.html#17656">[ thread ]</a>
              <a href="subject.html#17656">[ subject ]</a>
              <a href="author.html#17656">[ 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>