<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=4561&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / What necessitates these categories of systemd-related files?]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=4561</link>
		<description><![CDATA[The most recent posts in What necessitates these categories of systemd-related files?.]]></description>
		<lastBuildDate>Wed, 13 Oct 2021 12:57:28 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: What necessitates these categories of systemd-related files?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32067#p32067</link>
			<description><![CDATA[<p>as long as systemd has no control, fear not.</p>]]></description>
			<author><![CDATA[dummy@example.com (hevidevi)]]></author>
			<pubDate>Wed, 13 Oct 2021 12:57:28 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32067#p32067</guid>
		</item>
		<item>
			<title><![CDATA[Re: What necessitates these categories of systemd-related files?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32060#p32060</link>
			<description><![CDATA[<div class="quotebox"><cite>einpoklum wrote:</cite><blockquote><div><p>I want to make golinux&#039; question from the sticky thread more specific. He asked:</p></div></blockquote></div><p>Note that I posted that thread.&#160; I did not write it.&#160; Also . . .<br /><span class="bbu"><a href="https://dev1galaxy.org/viewtopic.php?pid=31788#p31788" rel="nofollow">https://dev1galaxy.org/viewtopic.php?pid=31788#p31788</a></span></p><div class="quotebox"><cite>einpoklum wrote:</cite><blockquote><div><p>But I&#039;m not interested in the binary response. Rather, I&#039;m looking at the different categories of files I can identify on my system, and would like to know why we (or perhaps I should say you Devuan maintainers) can&#039;t make them go away.</p></div></blockquote></div><p>1. It would be a lot of busy work that would serve no functional benefit.&#160; Those files just sit there and afaik do nothing.&#160; IOW the &quot;problem&quot; is in the mind not in reality.</p><p>2. Devuan maintainers work on packages that are essential for Devuan to function. You are, of course, welcome to take on such a project if you like.&#160; That&#039;s the way free software works.&#160; <img src="https://dev1galaxy.org/img/smilies/smile.png" width="15" height="15" alt="smile" /></p>]]></description>
			<author><![CDATA[dummy@example.com (golinux)]]></author>
			<pubDate>Tue, 12 Oct 2021 22:04:04 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32060#p32060</guid>
		</item>
		<item>
			<title><![CDATA[What necessitates these categories of systemd-related files?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32057#p32057</link>
			<description><![CDATA[<p>I want to make Katolaz&#039; question (quoted by golinux) from the sticky thread more specific. He asked:</p><p><strong><a href="https://dev1galaxy.org/viewtopic.php?id=1925" rel="nofollow">Why are systemd files present in Devuan?</a></strong></p><p>But I&#039;m not interested in the binary response. Rather, I&#039;m looking at the different categories of files I can identify on my system, and would like to know why we (or perhaps I should say you Devuan maintainers) can&#039;t make them go away. </p><p>So, here&#039;s my categorization:</p><ol class="decimal"><li><p>files under systemd-only directories: <span class="bbc">/etc/systemd</span>, <span class="bbc">/lib/systemd</span>, <span class="bbc">/usr/lib/systemd</span>, <span class="bbc">/var/lib/systemd/deb-systemd-helper-enabled/</span>, <span class="bbc">/var/lib/systemd/deb-systemd-user-enabled/</span></p><ol class="decimal"><li><p><span class="bbc">target.wants</span> directories</p></li><li><p><span class="bbc">.service</span> files</p></li><li><p><span class="bbc">.path</span> files</p></li><li><p><span class="bbc">.timer</span> files</p></li><li><p><span class="bbc">.socket</span> files</p></li><li><p><span class="bbc">.conf</span> files</p></li><li><p><span class="bbc">.target</span> files</p></li><li><p><span class="bbc">.dsh-also</span> files</p></li><li><p>files with other extensions (e.g. sleep, shutdown or no extension)</p></li></ol></li><li><p><span class="bbc">/usr/bin</span> files:</p><ul><li><p>debhelper<span class="bbc">dh_*</span> files and their man pages.</p></li><li><p>other files in <span class="bbc">/usr/bin</span>:</p><div class="codebox"><pre><code>deb-systemd-helper
deb-systemd-invoke
xscreensaver-systemd</code></pre></div></li></ul></li><li><p>apt daily file for systemd: <span class="bbc">/usr/lib/apt/apt.systemd.daily</span></p></li><li><p>lintian tag files for systemd service files &lt;- <em>Ok, I guess I don&#039;t want to remove those</em></p></li><li><p>Empty directories or subdirectories of other systemd-related directories</p></li></ol><p>For each of these categories - why can&#039;t we get rid of these files, i.e. avoid them being installed?</p><p>PS - I am willing to accept answers such as &quot;do not want to maintain variants of a large number of packages merely for avoiding them installing their own one or two systemd-related files&quot;. But then - would it not be possible to hot-patch such packages to drop those files? e.g. based on directory prefix filters?</p>]]></description>
			<author><![CDATA[dummy@example.com (einpoklum)]]></author>
			<pubDate>Tue, 12 Oct 2021 21:12:18 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32057#p32057</guid>
		</item>
	</channel>
</rss>
