summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-July/017657.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017657.html')
-rw-r--r--zarb-ml/mageia-dev/2012-July/017657.html163
1 files changed, 163 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017657.html b/zarb-ml/mageia-dev/2012-July/017657.html
new file mode 100644
index 000000000..6d09daa6c
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-July/017657.html
@@ -0,0 +1,163 @@
+<!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=%3C500EBF62.3%40colin.guthr.ie%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="017656.html">
+ <LINK REL="Next" HREF="017665.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] %{_unitdir} after /usr move</H1>
+ <B>Colin Guthrie</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=%3C500EBF62.3%40colin.guthr.ie%3E"
+ TITLE="[Mageia-dev] %{_unitdir} after /usr move">mageia at colin.guthr.ie
+ </A><BR>
+ <I>Tue Jul 24 17:29:38 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="017656.html">[Mageia-dev] %{_unitdir} after /usr move
+</A></li>
+ <LI>Next message: <A HREF="017665.html">[Mageia-dev] Weird boost subpackage (lib64 in i586)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#17657">[ date ]</a>
+ <a href="thread.html#17657">[ thread ]</a>
+ <a href="subject.html#17657">[ subject ]</a>
+ <a href="author.html#17657">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>'Twas brillig, and nicolas vigier at 24/07/12 15:35 did gyre and gimble:
+&gt;<i> On Tue, 24 Jul 2012, Colin Guthrie wrote:
+</I>&gt;<i>
+</I>&gt;&gt;<i> 'Twas brillig, and Olav Vitters at 24/07/12 15:11 did gyre and gimble:
+</I>&gt;&gt;&gt;<i> $ rpm -E '%{_unitdir}'
+</I>&gt;&gt;&gt;<i> /lib/systemd/system
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> This should show:
+</I>&gt;&gt;&gt;<i> /usr/lib/systemd/system
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> I see that it is defined in two places:
+</I>&gt;&gt;&gt;<i> 1. /etc/rpm/macros.d/20build.macros: %_unitdir /lib/systemd/system
+</I>&gt;&gt;&gt;<i> 2. /usr/lib/rpm/macros.systemd: %_unitdir /usr/lib/systemd/system
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> The latter obviously provides the right setting. But I guess due to
+</I>&gt;&gt;&gt;<i> ordering and so on it picks up the setting from 20build.macros.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> This is preventing me to package NetworkManager properly (I prefer
+</I>&gt;&gt;&gt;<i> relying on %{_unitdir} to give me the location, so the spec still works
+</I>&gt;&gt;&gt;<i> on Mageia 2).
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Could someone fix this?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Yeah this was on my to-fix list.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> As far as I'm aware the file in /usr/lib/rpm/macros.systemd will not be
+</I>&gt;&gt;<i> looked at at all anyway as it's not in any kind of magical .d folder.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> I would like to see the following changes:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> 1) We define a /usr/lib/rpm/macros.d/ folder.
+</I>&gt;&gt;<i> 2) Any packages shipping file in the /etc/ folder should change and use
+</I>&gt;&gt;<i> /usr/lib instead (/etc should be for admin overrides, NOT for general
+</I>&gt;&gt;<i> packaging).
+</I>&gt;&gt;<i> 3) We include the systemd macos in the /usr/lib/rpm/macos.d/ folder.
+</I>&gt;<i>
+</I>&gt;<i> This looks like a good idea.
+</I>
+Cool.
+
+&gt;&gt;<i> 4) Any files shipping systemd units require systemd-devel to ensure they
+</I>&gt;&gt;<i> have the macro.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> While steps 1-3 are probably OK (just need work) I'm not sure if
+</I>&gt;&gt;<i> requiring systemd-devel is overkill when all they need is a small part
+</I>&gt;&gt;<i> of it. I could potentially create a systemd-unit-devel package which
+</I>&gt;&gt;<i> only contained the neccesary stuff which would be lighter on the
+</I>&gt;&gt;<i> requirements front but I'm also against too much fragmentation here, so
+</I>&gt;&gt;<i> I'd be tempted to just say &quot;require systemd-devel&quot; and sod the
+</I>&gt;&gt;<i> not-strictly-necessary stuff it might end up pulling in.
+</I>&gt;<i>
+</I>&gt;<i> Are you talking about buildrequires ?
+</I>
+Yeah, sorry, this was all on the BuildRequires front. Like I said, I'm
+fairly tempted to just make such packages BuildRequire systemd-devel and
+forget about it rather than spend time splitting things up just to save
+a few seconds on the build time.
+
+Col
+
+--
+
+Colin Guthrie
+colin(at)mageia.org
+<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
+
+Day Job:
+ Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
+Open Source:
+ Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
+ PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
+ Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="017656.html">[Mageia-dev] %{_unitdir} after /usr move
+</A></li>
+ <LI>Next message: <A HREF="017665.html">[Mageia-dev] Weird boost subpackage (lib64 in i586)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#17657">[ date ]</a>
+ <a href="thread.html#17657">[ thread ]</a>
+ <a href="subject.html#17657">[ subject ]</a>
+ <a href="author.html#17657">[ 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>