Automated build

Antiz96 · Oct 14, 2024 · 1bc2ed0 · 1bc2ed0
1 parent 4321290
commit 1bc2ed0
Show file tree

Hide file tree

Showing 5 changed files with 521 additions and 2 deletions.
diff --git a/public/blog/index.html b/public/blog/index.html
@@ -330,6 +330,18 @@
   >
 
 
+        <div class="post custom-post">
+          <div class="post__content">
+            <a class="" href="/blog/maintaining-and-building-alpine-packages-from-arch-linux/" title="Maintaining and building Alpine packages from Arch Linux"><h3>Maintaining and building Alpine packages from Arch Linux</h3></a>
+            <div class="post__footer">14 October 2024</div>
+            <p><h2 id="alpine-packaging-tooling-are-now-available-in-the-arch-linux-extra-repository">Alpine packaging tooling are now available in the Arch Linux [extra] repository!</h2>
+<p>I recently added the <a href="https://gitlab.alpinelinux.org/alpine/abuild">abuild</a> and <a href="https://gitlab.alpinelinux.org/Leo/atools">atools</a> Alpine packaging tooling (including <code>abuild rootbld</code> to build Alpine packages in a clean chroot) to the Arch-Linux [extra] repository.</p>
+<p>This enables the Alpine packaging workflow directly from Arch Linux, allowing Arch users that <em>also</em> contributes to Alpine Linux (like I do) to run some Alpine packaging commands / tools, such as <code>newapkbuild</code>, <code>apkbuild-lint</code>, <code>apkbuild-fixer</code>, <code>abuild checksum</code>, <code>abuild rootbld</code>, &hellip;, without the necessity to rely on an separate Alpine installation (e.g. a container / chroot or a VM).</p></p>
+            <p>[...]</p>
+            <a class="custom-readmore" href="/blog/maintaining-and-building-alpine-packages-from-arch-linux/" title="Maintaining and building Alpine packages from Arch Linux">Read More</a>
+          </div>
+        </div>
+
         <div class="post custom-post">
           <div class="post__content">
             <a class="" href="/blog/what-should-we-learn-from-the-xz-situation-as-package-maintainers/" title="What should we learn from the XZ situation as Package Maintainers?"><h3>What should we learn from the XZ situation as Package Maintainers?</h3></a>

diff --git a/public/blog/index.xml b/public/blog/index.xml
@@ -6,7 +6,20 @@
     <description>Recent content in Blog on Robin Candau</description>
     <generator>Hugo -- gohugo.io</generator>
     <language>en-us</language>
-    <lastBuildDate>Wed, 03 Apr 2024 14:56:04 +0200</lastBuildDate><atom:link href="https://antiz.fr/blog/index.xml" rel="self" type="application/rss+xml" />
+    <lastBuildDate>Mon, 14 Oct 2024 10:42:00 +0200</lastBuildDate><atom:link href="https://antiz.fr/blog/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Maintaining and building Alpine packages from Arch Linux</title>
+      <link>https://antiz.fr/blog/maintaining-and-building-alpine-packages-from-arch-linux/</link>
+      <pubDate>Mon, 14 Oct 2024 10:42:00 +0200</pubDate>
+
+      <guid>https://antiz.fr/blog/maintaining-and-building-alpine-packages-from-arch-linux/</guid>
+
+        <description>&lt;h2 id=&#34;alpine-packaging-tooling-are-now-available-in-the-arch-linux-extra-repository&#34;&gt;Alpine packaging tooling are now available in the Arch Linux [extra] repository!&lt;/h2&gt;
+&lt;p&gt;I recently added the &lt;a href=&#34;https://gitlab.alpinelinux.org/alpine/abuild&#34;&gt;abuild&lt;/a&gt; and &lt;a href=&#34;https://gitlab.alpinelinux.org/Leo/atools&#34;&gt;atools&lt;/a&gt; Alpine packaging tooling (including &lt;code&gt;abuild rootbld&lt;/code&gt; to build Alpine packages in a clean chroot) to the Arch-Linux [extra] repository.&lt;/p&gt;
+&lt;p&gt;This enables the Alpine packaging workflow directly from Arch Linux, allowing Arch users that &lt;em&gt;also&lt;/em&gt; contributes to Alpine Linux (like I do) to run some Alpine packaging commands / tools, such as &lt;code&gt;newapkbuild&lt;/code&gt;, &lt;code&gt;apkbuild-lint&lt;/code&gt;, &lt;code&gt;apkbuild-fixer&lt;/code&gt;, &lt;code&gt;abuild checksum&lt;/code&gt;, &lt;code&gt;abuild rootbld&lt;/code&gt;, &amp;hellip;, without the necessity to rely on an separate Alpine installation (e.g. a container / chroot or a VM).&lt;/p&gt;</description>
+
+    </item>
+
     <item>
       <title>What should we learn from the XZ situation as Package Maintainers?</title>
       <link>https://antiz.fr/blog/what-should-we-learn-from-the-xz-situation-as-package-maintainers/</link>