<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SleepMap (Posts about arch-repo-management)</title><link>https://sleepmap.de/</link><description></description><atom:link href="https://sleepmap.de/categories/arch-repo-management.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2022 &lt;a href="mailto:dave@sleepmap.de"&gt;David Runge&lt;/a&gt; 
&lt;a rel="license" href="https://creativecommons.org/licenses/by-nc-sa/4.0/"&gt;CC BY-NC-SA 4.0&lt;/a&gt;</copyright><lastBuildDate>Mon, 12 Dec 2022 10:30:48 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Packaging for Arch Linux</title><link>https://sleepmap.de/2022/packaging-for-arch-linux/</link><dc:creator>David Runge</dc:creator><description>&lt;div&gt;&lt;p&gt;In &lt;a class="reference external" href="https://sleepmap.de/2022/arch-a-recap"&gt;Arch, a recap&lt;/a&gt; I elaborated a bit
on my reasons for getting involved with Arch Linux. In this post I would like
to highlight a few technical details and give a "behind the scenes" when it
comes to packaging on and for Arch Linux.
This post is written from the viewpoint of a distribution packager, but it
is likely to contain information also useful to people packaging on different
distributions or for private purposes.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://sleepmap.de/2022/packaging-for-arch-linux/"&gt;Read more…&lt;/a&gt; (22 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>arch linux</category><category>arch-repo-management</category><category>dbscripts</category><category>packaging</category><category>reproducible builds</category><guid>https://sleepmap.de/2022/packaging-for-arch-linux/</guid><pubDate>Wed, 06 Apr 2022 11:22:53 GMT</pubDate></item></channel></rss>