summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006649.html
blob: 0fee1d830ba876d3e111acf21d1d278900e72b8d (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
142
143
144
145
146
147
148
149
150
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] [Mageia 2 specifications] Systemd or not systemd
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia%202%20specifications%5D%20Systemd%20or%20not%20systemd&In-Reply-To=%3Cm37h7k4g09.fsf%40euphor.blino.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="006652.html">
   <LINK REL="Next"  HREF="006650.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] [Mageia 2 specifications] Systemd or not systemd</H1>
    <B>Olivier Blin</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia%202%20specifications%5D%20Systemd%20or%20not%20systemd&In-Reply-To=%3Cm37h7k4g09.fsf%40euphor.blino.org%3E"
       TITLE="[Mageia-dev] [Mageia 2 specifications] Systemd or not systemd">mageia at blino.org
       </A><BR>
    <I>Fri Jul 15 01:08:38 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="006652.html">[Mageia-dev] [Mageia 2 specifications] Systemd or not systemd
</A></li>
        <LI>Next message: <A HREF="006650.html">[Mageia-dev] [Mageia 2 specifications] Systemd or not systemd
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6649">[ date ]</a>
              <a href="thread.html#6649">[ thread ]</a>
              <a href="subject.html#6649">[ subject ]</a>
              <a href="author.html#6649">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Colin Guthrie &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>&gt; writes:

&gt;&gt;<i> Secondly, what should be the correct way of supporting systemd in a
</I>&gt;&gt;<i> package? In Mandriva, I thought on adding a --with flag to
</I>&gt;&gt;<i> enable/disable systemd, but in most cases it does (almost) nothing. All
</I>&gt;&gt;<i> services which want to support systemd only need to place their files
</I>&gt;&gt;<i> into /lib/systemd - and that's it. Should we support opting-out of
</I>&gt;&gt;<i> systemd in specs? I believe fcrozat is having the same dilemma in SuSE
</I>&gt;&gt;<i> now as well, and he settled on some common packaging macros.
</I>&gt;<i>
</I>&gt;<i> IMO, unless something goes horribly wrong with systemd (which I very
</I>&gt;<i> seriously doubt will happen - it's actually been amazing to watch this
</I>&gt;<i> project from birth to wide adoption) I'd say we just jump right in and
</I>&gt;<i> package the units unconditionally. They don't really take up much space
</I>&gt;<i> and do nothing if you choose to not use it for the time being. I think
</I>&gt;<i> by mga3 we'll likely *only* offer systemd (if not in mga2), so I'd say
</I>&gt;<i> putting in effort to opt out now is pretty much not going to be worth it.
</I>
I agree, it does not seem useful to avoid shipping systemd services.

Though, when systemd is enabled, what happens if one has both systemd +
sysvinit services files installed for a given package?
Will the initscript be run in addition to the systemd service?

&gt;&gt;<i> Almost finally, should the systemd files belong to the main package, the
</I>&gt;&gt;<i> same way as they do with initscripts-based one (e.g., the package would
</I>&gt;&gt;<i> provide /lib/systemd/system/%{name}.service together with
</I>&gt;&gt;<i> %_sysconfig/rc.d/init.d/%{name} for example), with no extra subpackages
</I>&gt;&gt;<i> or flags - or should all systemd-specific files go into %{name}-systemd
</I>&gt;&gt;<i> package for example? What do you think?
</I>&gt;<i>
</I>&gt;<i> I vote to put them in the same place as the initscripts-based ones. As I
</I>&gt;<i> predicted above, I reckon it won't take too long for systemd to be the
</I>&gt;<i> only system offered and obsoleting all those subpackages would be a bit
</I>&gt;<i> of a PITA down the line. And if systemd isn't used those files do
</I>&gt;<i> nothing, so no harm done.
</I>
Agreed as well.

&gt;&gt;<i> And finally, what does seems to be the best way of starting to use
</I>&gt;&gt;<i> systemd in cauldron? I have thought on 3 alternatives:
</I>&gt;&gt;<i>  - easy way, only having it packaged, but not
</I>&gt;&gt;<i> providing/obsoleting/conflicting with sysvinit. This way, it will work
</I>&gt;&gt;<i> when kernel is booted with init=/bin/systemd (the least invasive way)
</I>&gt;&gt;<i>  - compatible way (like in Mandriva) - it is available, systemd-sysvinit
</I>&gt;&gt;<i> conflicts with sysvinit, so if someone installs systemd-sysvinit,
</I>&gt;&gt;<i> sysvinit goes away and systemd is run by default. This seems to be the
</I>&gt;&gt;<i> most sane way to me (but I could be biased), and it is easiest one for
</I>&gt;&gt;<i> testing
</I>&gt;&gt;<i>  - ultimate way - systemd provides and obsoletes sysvinit and its
</I>&gt;&gt;<i> goodies. This way, systemd will be the only one (e.g., highlander
</I>&gt;&gt;<i> style). This is how fedora did it if I am not mistaken, but I am not
</I>&gt;&gt;<i> sure if it the best way.
</I>&gt;&gt;<i> 
</I>&gt;&gt;<i> So, that's it for now from my part..
</I>&gt;<i>
</I>&gt;<i> I'd like option 2 please! :) It doesn't exclude using option 1 along
</I>&gt;<i> with it (I was doing this for a while), so it's most flexible.
</I>
Option 2 seems good as well, but does it really have to uninstall
sysvinit? Isn't it enough to put some alternatives symlinks for
/sbin/init?

-- 
Olivier Blin - blino
</PRE>































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="006652.html">[Mageia-dev] [Mageia 2 specifications] Systemd or not systemd
</A></li>
	<LI>Next message: <A HREF="006650.html">[Mageia-dev] [Mageia 2 specifications] Systemd or not systemd
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6649">[ date ]</a>
              <a href="thread.html#6649">[ thread ]</a>
              <a href="subject.html#6649">[ subject ]</a>
              <a href="author.html#6649">[ 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>