diff options
authorCem Keylan <cem@ckyln.com>2021-05-25 23:41:35 +0300
committerCem Keylan <cem@ckyln.com>2021-05-25 23:41:35 +0300
commit5f70d9dd4686b304faac20ea1c0c23450042bacd (patch)
parent9ed7cca233c82760e2b12f704af7df690ba4adec (diff)
site: Add new blog postHEADmaster
1 files changed, 49 insertions, 0 deletions
diff --git a/blog/20210525.org b/blog/20210525.org
new file mode 100644
index 0000000..e19039a
--- /dev/null
+++ b/blog/20210525.org
@@ -0,0 +1,49 @@
+#+TITLE: May 2021 News Post
+#+DATE: <2021-05-25 Tue>
+#+AUTHOR: Cem Keylan
+Welcome to May! It has been a rather quiet month, mostly dedicated to fixing
+some small bugs and working on some features.
+#+TOC: headlines 1 local
+** Fossil support and new repository backend
+:CUSTOM_ID: fossil-support
+In the [[file:20210415.org::#fossil][previous news post]] I mentioned adding fossil support to the package
+manager. Fossil support is now merged to the trunk branch of the package
+manager, and I have completely rewritten the repository backend which has
+better performance and is easier to extend. There are still some changes to
+make, but the feature will be added in the =6.1.0= release.
+** Moving IRC channel
+:CUSTOM_ID: moving-irc-channel
+After the recent controversies surrounding Freenode, we have also switched to
+the new Libera IRC network. Since our previous logger =globbot= is also shutting
+down, I have set up an IRC logger powered by [[https://git.causal.agency/litterbox][litterbox]]. The IRC logs can be
+found on [[https://irclogs.carbslinux.org]]. The website includes both a searchable
+web interface, and plaintext dumps of daily logs. Even though the channel is
+low-volume, I think logging it is extremely important.
+** New i686 release
+:CUSTOM_ID: new-i686-release
+I have decided to make an i686 release last week because it was really outdated,
+but it will likely be the last one depending on its use on the few following
+months. If you are interested in keeping support for the architecture, feel free
+to join the IRC channel to let me know. Maintaining i686 isn't really much of a
+burdon on me, but there is no point in maintaining an architecture that isn't
+used by anyone.
+Compared to the last month, there aren't much news, and there have been other
+things that I needed to attend to. I started writing this post on the 13th, and
+only had the time to finish it now!
+See you on the next post!