summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-July/017656.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017656.html')
-rw-r--r--zarb-ml/mageia-dev/2012-July/017656.html141
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017656.html b/zarb-ml/mageia-dev/2012-July/017656.html
new file mode 100644
index 000000000..81a5913cb
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-July/017656.html
@@ -0,0 +1,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>