<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>slackware on Rise of the Leviathan</title>
    <link>https://www.liwjatan.org/tags/slackware/</link>
    <description>Recent content in slackware on Rise of the Leviathan</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Thu, 24 Feb 2022 17:12:00 +0100</lastBuildDate><atom:link href="https://www.liwjatan.org/tags/slackware/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Repository for Slackware 15.0</title>
      <link>https://www.liwjatan.org/blog/2022/02/slackware-15.0/</link>
      <pubDate>Thu, 24 Feb 2022 17:12:00 +0100</pubDate>
      
      <guid>https://www.liwjatan.org/blog/2022/02/slackware-15.0/</guid>
      <description>On February 2nd, 2022 Pat released Slackware 15.0. Now, with an unfortunately sizable delay, I branched off my package repository to properly support Slackware 15.0 as well.
Why so late? Like I mentioned in my last past about the repo, I&amp;rsquo;m maintaining it in my free time and there just hasn&amp;rsquo;t been enough of that lately. Between work and an absolutely wonderful skiing trip with my family I had almost no time at all to look at Slackware.</description>
    </item>
    
    <item>
      <title>Slackware Repository</title>
      <link>https://www.liwjatan.org/blog/2021/12/slackware-repo/</link>
      <pubDate>Sat, 25 Dec 2021 13:52:04 +0100</pubDate>
      
      <guid>https://www.liwjatan.org/blog/2021/12/slackware-repo/</guid>
      <description>Some time ago I started making a slackware package repository for software I need in my systems not included in the core. I spent some time getting processes in place and getting used to them. By now, those are all fairly settled and I feel confident in letting other people know about them.
First off, however, there&amp;rsquo;s some caveats. The repository is currently based on -current, and for x86_64 only. I have no interest in making a 32bit repo as the overhead would just be too big.</description>
    </item>
    
  </channel>
</rss>
