website: switch to hugo

14 files changed, 752 insertions, 0 deletions

diff --git a/content/blog/20200128.org b/content/blog/20200128.org
new file mode 100644
index 0000000..97b771a
--- /dev/null
+++ b/content/blog/20200128.org
@@ -0,0 +1,17 @@
+#+TITLE: Switching to New Website
+#+DATE: 2020-01-28
+#+AUTHOR: Cem Keylan
+#+ALIASES[]: /blog/20200128.html
+
+In case you haven't seen it before, this website was powered by [[http://werc.cat-v.org][werc]]. And even
+though I liked it really much, it was too powerful for a small website like
+this.
+
+So I have decided to reimplement this website with my own static generation
+scripts. The source will probably be on [[https://git.carbslinux.org/website/log.html][its git repository]] when I decide to
+publish the website.
+
+The generation requires Plan9 programs, although I have used them just for my
+enthusiasm. I have built the site with a combination of mk (instead of make),
+rc, and POSIX sh. I am not yet exactly familiar with rc, but I will replace the
+shell scripts when I feel like I can.
diff --git a/content/blog/20200406.org b/content/blog/20200406.org
new file mode 100644
index 0000000..c993b6f
--- /dev/null
+++ b/content/blog/20200406.org
@@ -0,0 +1,74 @@
+#+TITLE: Roadmap for Carbs
+#+AUTHOR: Cem Keylan
+#+DATE: <2020-04-06 Mon>
+#+ALIASES[]: /blog/20200406.html
+
+It has been a busy week. There are lots of changes in direction, and more to
+come. I want to talk a little about all of them.
+
+** Carbs Linux Server Going Down
+:PROPERTIES:
+:CUSTOM_ID: carbs-linux-server-going-down
+:END:
+
+It became harder to maintain and pay for the server, and I will be shutting it
+down in May. I am currently in the phase of carrying over everything to [[https://github.com/CarbsLinux][Github]].
+The repository and the website is served on Github now. I have also moved the
+[[https://github.com/CarbsLinux/wiki/wiki][Wiki]] to Github and anyone can edit it there. There are some outdated posts that
+I will be fixing around this week.
+
+I am not quite sure where to store the downloads page now. But I will be
+switching that to a new source as well. (Maybe SourceHut?)
+
+I feel a little sad for switching, but serving on Github is faster, cheaper, and
+hassle-free.
+
+** Forking KISS
+:PROPERTIES:
+:CUSTOM_ID: forking-kiss
+:END:
+
+I had a personal fork of KISS, which I enjoyed thoroughly. I didn't intend to
+make it the default when I started it, but it has matured enough to be so. The
+package manager can now be found on [[https://github.com/CarbsLinux/kiss][this repository]]. See it for the added
+changes.
+
+This will be a change for the better, as I can develop the package manager as it
+fits my views.
+
+** Small Changes on the Website
+:PROPERTIES:
+:CUSTOM_ID: small-changes-on-the-website
+:END:
+
+I have made some small changes on the website. The build is not dependent on
+Plan9 utilities anymore. It was fun messing around with =rc= and =mk=, but they
+are quite limited compared to POSIX shell.
+
+RSS feeds are finally working as intended, both for the [[https://carbslinux.org/news.xml][news]] section, and the
+[[https://carbslinux.org/rss.xml][blog]] section.
+
+You can see every page's =.txt= output at the end of the page by clicking 'View
+Page Source'. Meanwhile, I will be updating some pages to be a little more
+'human-readable'.
+
+** Outsources Repository
+:PROPERTIES:
+:CUSTOM_ID: outsources-repository
+:END:
+
+I have opened an =outsource= repository, which I will be pushing this week. I
+will add a new post when I am ready to push it. I think it will be interesting,
+it will also make more sense about the changes I have added to the package
+manager. The now empty repository, can be found [[https://github.com/CarbsLinux/outsource][here]]!
+
+** New Tarball
+:PROPERTIES:
+:CUSTOM_ID: new-tarball
+:END:
+
+Finally, I have released a new tarball today, which can be obtained from the
+[[https://dl.carbslinux.org/releases][downloads page]].
+
+I am planning to add more of these update posts as I'm feeling better about the
+website structure overall.
diff --git a/content/blog/20200410.org b/content/blog/20200410.org
new file mode 100644
index 0000000..8bdf57a
--- /dev/null
+++ b/content/blog/20200410.org
@@ -0,0 +1,22 @@
+#+TITLE: Outsource Repository Concept
+#+AUTHOR: Cem Keylan
+#+DATE: <2020-04-10 Fri>
+#+ALIASES[]: /blog/20200410.html
+
+In April 3rd, I have added submodule support for Carbs Linux's fork of =kiss=.
+Now, from that sentence, it really doesn't sound exciting at all. But in
+reality, it opens a path to lots of creative output, and a better way to manage
+multi-user repositories (such as KISS Community).
+
+When managing a repository of submodules, the repository maintainer's only job
+is to deal with adding packages. A package maintainer doesn't have to wait for
+the repository maintainer to update their packages, as they are only making the
+changes to their own repositories.
+
+This way, an end-user can also track from their preferred maintainers, and do
+that with the tidyness of a single repository in their =KISS_PATH=.
+
+Carbs Linux now has an outsource repository for some packages. Firefox and its
+dependencies have been purged from the main repository, but can be found on it.
+
+[[https://github.com/CarbsLinux/outsource]]
diff --git a/content/blog/20200508.org b/content/blog/20200508.org
new file mode 100644
index 0000000..8de5de0
--- /dev/null
+++ b/content/blog/20200508.org
@@ -0,0 +1,114 @@
+#+TITLE: The Relation of Carbs and KISS
+#+AUTHOR: Cem Keylan
+#+DATE: <2020-05-08 Fri>
+#+ALIASES[]: /blog/20200508.html
+
+Since I have forked KISS, I have received many questions that can be summarized
+as "Why?". I have realized that I never truly answered this question. That's the
+reason I am writing this post, to give some background on Carbs, and some
+differences between KISS Linux and Carbs Linux for anyone who may be wondering.
+Perhaps I could make this a "FAQ" page later on.
+
+** History
+:PROPERTIES:
+:CUSTOM_ID: history
+:END:
+
+I had the idea of creating my own Linux distribution since the May of 2019. Back
+then, I had my own [[https://linuxfromscratch.org][Linux from Scratch]] build, and I wanted to slim it down my
+own way and replace the software (with musl,sbase,etc.). The name Carbs Linux
+was in my mind since then. I wanted to write my own package manager, but I
+wasn't satisfied with anything I had built.
+
+I had written some incomplete package managers (all named =fat=) and I quickly
+threw them into the trash can, where they honestly belonged. I would want to
+share them with you for laughs, but my hard-drive got wiped and I have a problem
+of not doing an "initial commit" until a program I write is in a usable state.
+
+I have obtained the 'carbslinux.org' domain name in September 2019, but then
+life got on the way, and I stopped for a long time.
+
+One day on Reddit, I saw Dylan's post on [[https://reddit.com/r/unixporn][r/unixporn]] about KISS, and I really
+thought that it was interesting. Here is my [[https://www.reddit.com/r/unixporn/comments/ducd34/sowm_kiss_d/f7lua7x][comment]] to Dylan on that post. I
+checked out the package manager and the repository. The packaging system was
+extremely clean and well-thought. I decided to give it a go and fork KISS.
+
+** Differences between KISS and Carbs
+:PROPERTIES:
+:CUSTOM_ID: differences-between-kiss-and-carbs
+:END:
+
+Now, I still baffle when people ask me this question. My intention was never to
+create a distribution with specific differences between KISS. My intention was
+being my own BDFL of a distribution I maintain. There are lots of differences
+between the main repositories, but they are subtle and not worth talking about.
+I personally never even installed KISS Linux on my system. So Carbs, isn't
+something like a downstream fork of KISS, it is just a distribution that was
+initially based on KISS.
+
+I try to contribute as much as I can to KISS Linux. I think that it is a
+brilliant distribution, and it was a great starting point for Carbs. I am really
+grateful to Dylan and all the other contributors.
+
+** What I'm working on now
+:PROPERTIES:
+:CUSTOM_ID: what-im-working-on-now
+:END:
+
+Currently I have a few projects that I'm working on for Carbs. These are,
+
+A BSD port for Carbs. For a while, I have been working on BSD compatibility on
+my fork of the [package manager]. I have tested, without any more issues, on
+OpenBSD and FreeBSD. The biggest issues remaining are choosing a vendor for BSD,
+packaging the BSD source, and providing a minimal base (like busybox for BSD).
+If you aren't familiar with BSD, it has a single source code for all of the
+utilities (kernel, command line programs, etc.). Contributions (even chipping in
+ideas) are very welcome.
+
+Adding binary package distribution support natively to the package manager.
+Biggest issue in small/old computers are compile times. This feature is for the
+bigger packages such as webkit, clang, llvm that take a considerable amount of
+time. Some computers with low memories cannot even compile firefox/webkit.
+
+Adding rsync repository support to the package manager. This is not a current
+issue, but rather a futureproofing. As time passes, distribution repositories
+grow larger. KISS and Carbs are young distributions without this problem right
+now. But in something like 5 years, this size will presumably increase to
+hundreds of megabytes. At that point it will be pointless to have the repository
+sources unless you specifically need them.
+
+** What's up with all the init/service daemons?
+:PROPERTIES:
+:CUSTOM_ID: whats-up-with-all-the-init-service-daemons
+:END:
+
+If you have ever checked the [[https://github.com/carbslinux/repository][repository]], you may have noticed that there are
+lots of init/service related packages. I have had my fair share of time with all
+of them, and it is an area that I am really interested in. I have even written
+my own [[https://github.com/cemkeylan/shinit][init daemon]] and [[https://github.com/cemkeylan/sysmgr][service supervisor]]. I maintain all those packages on KISS
+Community Repository as well with the exception of busybox. Those are, =busybox
+init/runit=, =runit=, =sinit=, and =sysmgr=. I would definitely recommend
+checking out =shinit= and =sysmgr=.
+
+** Why I don't publicize Carbs
+:PROPERTIES:
+:CUSTOM_ID: why-i-dont-publicize-carbs
+:END:
+
+There are a couple of reasons I don't publicize Carbs a lot.
+
+KISS is the better alternative in terms of support and community. I work on
+maintaining this distribution just as hard as Dylan, but in the end, Carbs is
+based on his original hard work, and I believe that he deserves the recognition
+more than I do.
+
+Since I cannot answer questions like "What is the difference?", I prefer staying
+as the silent sibling project of KISS Linux. Plus, there is no point in dividing
+the newly-emerging community in half.
+
+That's not because I don't have ideas for the future of Carbs, I do. I just
+think that I will deserve the recognition once those above lists are checked.
+
+I think that's about it, if you have questions you can send me a mail, ping me
+on IRC (my handle is =merakor=), and I will be happy to answer. Maybe your
+question fits this post, and I can update it to thoroughly give an explanation.
diff --git a/content/blog/20200528.org b/content/blog/20200528.org
new file mode 100644
index 0000000..54a140b
--- /dev/null
+++ b/content/blog/20200528.org
@@ -0,0 +1,41 @@
+#+TITLE: kiss 2.0.0 and Overall Changes
+#+AUTHOR: Cem Keylan
+#+DATE: <2020-05-28 Thu>
+#+ALIASES[]: /blog/20200528.html
+
+Carbs Linux kiss version 2.0.0 has been released which introduces rsync
+repositories.
+
+Git is no longer a mandatory dependency for the package manager, every git
+source on the core repository has been replaced with https sources (sbase,
+sinit), and rootfs tarballs will no longer ship with git. Repositories in the
+upcoming tarball will be rsync repositories.
+
+Git is now on the =extra= repository and is still (optionally) used in the
+package manager.
+
+The idea behind this change is size reductions and increased speed with rsync.
+As I said on the previous post, git repositories get larger and larger over the
+time span. Currently my personal copy of the git repository is around 77MB and I
+have forked KISS Linux (as a shallow copy) around December. Obviously, I have
+commits that I ommitted. I tend to create commits I dislike, which I change with
+=git reset --soft HEAD^=, which doesn't actually remove the commits, etc. A user
+will have a repository much smaller than mine.
+
+This is a precaution with the added bonuses of speed and dropping a mandatory
+dependency.
+
+You can see the rest of the changelog [[https://github.com/CarbsLinux/kiss/blob/master/CHANGELOG.md][here]].
+
+** Binary Repositories
+:PROPERTIES:
+:CUSTOM_ID: binary-repository
+:END:
+
+A few days ago, I have also published [[https://github.com/CarbsLinux/kiss-bin][kiss-bin]], a first version for managing
+binary repositories. Currently, there are some caveats that I'll be fixing along
+the way. I decided not to include this in the package manager natively as
+managing the source based and binary based packages together adds levels of
+complexity that we do not want. Instead, this is an extension for kiss which
+sources the package manager as a library. I hope to see it being adopted by
+others interested on the matter as well.
diff --git a/content/blog/20200617.org b/content/blog/20200617.org
new file mode 100644
index 0000000..2524fb6
--- /dev/null
+++ b/content/blog/20200617.org
@@ -0,0 +1,89 @@
+#+TITLE: June 2020 News Post
+#+AUTHOR: Cem Keylan
+#+DATE: <2020-06-17 Wed>
+#+ALIASES[]: /blog/20200617.html
+
+This will be an active month for Carbs as major changes to the base and the
+package manager will be coming up.
+
+** Statically linking the base
+:PROPERTIES:
+:CUSTOM_ID: statically-linking-the-base
+:END:
+
+For the past couple of weeks I have been trying to simplify the base and
+statically link the core (mostly binaries rather than libraries). I usually see
+some people extremely opposed to static linking as I also see the opposite on
+people.
+
+I believe that binaries on the core should always be linked statically. This
+ensures that an SONAME bump to =libObscure.so= will not break the core
+functionality of your system, forcing you to use external resources to recover
+from such an issue. As long as you can compile, use core utilities, edit text,
+and access the web, you can solve any given issue on your system.
+
+However, I don't think that removing shared libraries is sensible either. Not
+every piece of software out there is good quality enough to be statically
+linked.
+
+** Major changes on the core repository
+:PROPERTIES:
+:CUSTOM_ID: major-changes-on-the-core-repository
+:END:
+
+There have been drastic changes to the core repository and the base rootfs this
+month (with more on the way). Right now changes are as follows.
+
+*** Removed from Core
+:PROPERTIES:
+:CUSTOM_ID: removed-from-core
+:END:
+- =git=
+- =libressl=
+- =grub=
+- =bison=
+- =dhcpcd=
+- =ubase=
+
+*** Added to Core
+:PROPERTIES:
+:CUSTOM_ID: added-to-core
+:END:
+- =bearssl=, as a =libressl= replacement
+- =byacc=, as a =bison= replacement
+
+*** Statically linked
+:PROPERTIES:
+:CUSTOM_ID: statically-linked
+:END:
+- =kiss=
+- =neatvi=
+- =mandoc=
+- =byacc=
+- =m4=
+- =e2fsprogs=
+- =make=
+- =pkgconf=
+- =sbase=
+- =libnl=
+- =wpa_supplicant=
+- =bearssl=
+
+** Making the wiki available offline
+:PROPERTIES:
+:CUSTOM_ID: making-the-wiki-available-offline
+:END:
+
+Soon, all documentation regarding Carbs Linux will be avaialable to be installed
+from the core repository in a =carbs-docs= package along with its own document
+crawler. Currently, the documentation regarding the installation process is a
+little outdated which will also receive some important updates.
+
+** ISO image for Carbs
+:PROPERTIES:
+:CUSTOM_ID: iso-image-for-carbs
+:END:
+
+I am thinking of releasing an ISO image in order to provide a standardized
+environment for installation along with installation helper tools in the spirit
+of =arch-install-scripts=. Let's see how that's going to play out.
diff --git a/content/blog/20200803.org b/content/blog/20200803.org
new file mode 100644
index 0000000..c2c2b6b
--- /dev/null
+++ b/content/blog/20200803.org
@@ -0,0 +1,72 @@
+#+TITLE: August 2020 News Post
+#+AUTHOR: Cem Keylan
+#+DATE: <2020-08-03 Mon>
+#+ALIASES[]: /blog/20200803.html
+
+We are having some stalls during this summer, as I am currently working on
+university-related stuff. Nonetheless, there are some important changes that I
+want to share in this month's post.
+
+#+TOC: headlines 1 local
+
+** Carbs Packaging Tools
+:PROPERTIES:
+:CUSTOM_ID: carbs-packaging-tools
+:END:
+
+This month I have reworked =kiss= into a new package manager, now renamed as
+=cpt=. Updating =kiss= will now bootstrap the new package manager, so you don't
+have to manually edit your system. If you don't like the idea of this, you can
+look up the =post-install= script on =core/kiss= and apply the changes manually.
+
+You will also need to rename your =KISS_*= variables to =CPT_*=. So, =KISS_PATH=
+becomes =CPT_PATH=.
+
+The rework changes the previous commands on the package manager into standalone
+tools, and move the package manager functions to a library. This makes it easier
+for a user to import functions and variables from the package manager, and
+extend the package manager with their own intended way. Previously this required
+ugly hacks and workarounds to use the package manager functions. I will be
+making use of these changes to re-implement binary package management functions
+as well.
+
+If you want to use the library on your script you can simply do this:
+
+#+BEGIN_SRC sh
+#!/bin/sh
+. cpt-lib
+(...)
+#+END_SRC
+
+There are obviously some clean-up and simplifications needed in this new
+tool-based package management method.
+
+** Docs
+:PROPERTIES:
+:CUSTOM_ID: docs
+:END:
+
+I have added documentation for the distribution, and finally updated the guide
+for installation. It is now /almost/ complete. These docs can be installed to
+your system for online viewing. I will also add a documentation crawler similar
+to how werc works (but as an offline viewer). You can find =carbs-docs= from
+the repository. Currently, the documentation lacks but I will be adding new
+stuff. These will solely be distribution specific documentation and will not be
+a wiki-like source. If anyone would like to contribute to a wiki-like
+documentation source, I would happily re-open the distribution wiki. You can
+find the source on [[https://github.com/CarbsLinux/docs]].
+
+** Re-opening the Carbs Linux server
+:PROPERTIES:
+:CUSTOM_ID: re-opening-the-carbs-linux-server
+:END:
+
+Back in May, I had shutdown the Carbs Linux server due to financial issues, but
+I am slowly reverting to the self-hosted model. Back then, the git repositories
+were mirrored to GitHub, and the management was overall much more flexible. The
+server used to run Carbs Linux as well (that was fun and horrifying at the same
+time). Now, I will be relaunching the git server which will be the upstream
+source before August 5. You can switch your remote, but GitHub will stay as a
+remote nonetheless.
+
+*EDIT:* The git-server is up!
diff --git a/content/blog/20201210.org b/content/blog/20201210.org
new file mode 100644
index 0000000..f945dc5
--- /dev/null
+++ b/content/blog/20201210.org
@@ -0,0 +1,23 @@
+#+TITLE: First Year of Carbs Linux
+#+AUTHOR: Cem Keylan
+#+DATE: <2020-12-10 Thu>
+#+ALIASES[]: /blog/20201210.html
+
+December 10, 2020 marks the first year after the initial release of Carbs Linux.
+When I forked the KISS Linux repository on the 9th of December, I was fairly new
+to package management. Carbs Linux used to be almost identical to KISS Linux. A
+lot has changed since then:
+
+- [2020 Jan 13] Replaced default init system to =sinit=
+- [2020 Jan 15] Packaged =WebKit2GTK=
+- [2020 May 17] Added =bearssl= on the testing repository
+- [2020 May 28] Added =rsync= repository support to kiss
+- [2020 Jun 03] Replaced =bison= with =byacc=
+- [2020 Jun 11] Replaced =libressl= with =bearssl=
+- [2020 Jun 24] Replaced =kiss= with =cpt=
+
+I have really enjoyed maintaining and developing this distribution, and I want
+to thank everyone who was involved in some way or another. While I have slowed
+down in development due to college workload, I am still actively maintaining all
+the packages on the repository. I do have some ideas that I am thinking of
+implementing during the semester break. Hope to see you all in January.
diff --git a/content/blog/20210303.org b/content/blog/20210303.org
new file mode 100644
index 0000000..bf7ad96
--- /dev/null
+++ b/content/blog/20210303.org
@@ -0,0 +1,84 @@
+#+TITLE: March 2021 News Post
+#+DATE: <2021-03-03 Wed>
+#+AUTHOR: Cem Keylan
+#+ALIASES[]: /blog/20210303.html
+
+Greetings! I am really happy to announce some few changes to the distribution. I
+wanted to write a new blog post to summarise them so you can get up to what is
+happening in Carbs Linux.
+
+#+TOC: headlines 1 local
+
+** Switching to Sourcehut
+:PROPERTIES:
+:CUSTOM_ID: switching-to-sourcehut
+:END:
+
+I have been thinking of moving development to [[srht:~carbslinux][Sourcehut]] for a while now. If your
+repository remotes reside at GitHub you are encouraged to switch them to
+Sourcehut. Mailing lists for discussion, development, and announcements have
+also been created for both the distribution, and the package manager using
+Sourcehut as the host. See the [[file:../mailing-lists.html][page on mailing lists]] for more information on
+subscribing to the mailing lists.
+
+This does mean that issue trackers now reside at Sourcehut, and I will be
+deactivating those in GitHub very soon. I have yet to decide whether on keeping
+the mirrors or deactivating them completely, but I will be giving three months
+of notice if it is decided to move away from GitHub completely. Regardless, the
+main repositories are still hosted at [[https://git.carbslinux.org][our own server]], and I have no intentions
+on changing that for the foreseeable future.
+
+*** State of our own Git repository
+
+In the near future, I will be moving our git server, and will be opening spots
+for other users, who want to make use of the git server. People can use it to
+serve their own =cpt= repositories, or personal projects that can be related to
+Carbs. I will post an announcement when this will happen, and a blog post that
+tells more about the new repository. Expect more by the end of March.
+
+** Wayland and Dbus
+:PROPERTIES:
+:CUSTOM_ID: wayland-and-dbus
+:END:
+
+There are new repositories for [[carbs-pkg:dbus/dbus][dbus]], and [[carbs-pkg:wayland/wayland][wayland]], which are still works in
+progress. These are meant to be options for those who /request/ it, and are not
+meant to be enforced package repositories. For example, any package outside of
+the ~dbus~ repository shouldn't require it to work, and shouldn't list it as a
+dependency. Packages can still be written using those as optional dependencies.
+
+This change also raises the question of whether Carbs is ditching Xorg or not.
+No, we are not ditching Xorg, Wayland is added as to serve an extra option for
+those who don't own graphics cards from some specific manufacturer.
+
+** Next release for CPT
+:PROPERTIES:
+:CUSTOM_ID: next-release-for-cpt
+:END:
+
+I had been working on the next major release for the package manager since
+December, and it is coming close to completion. This release focuses more on the
+library itself, and using the library more effectively on the contrib tools.
+Unfortunately, until this time, the library wasn't properly documented, and
+there weren't any unit tests for the library. Even though, the changes to the
+package manager are close to completion, documentation and tests are what is
+holding me from making the next release.
+
+** Website Update
+:PROPERTIES:
+:CUSTOM_ID: website-update
+:END:
+
+I have recently updated the website in its entirety so that it looks more
+appealing. I have updated the stylesheets and created a [[srht:~carbslinux/carbslinux-style][stylesheet repository]]
+and I am planning on extending it to use with other Carbs websites.
+
+The website is now generated using Emacs [[https://orgmode.org][Org Mode]], and its biggest advantage is
+that I can freely write posts without thinking about plaintext output, which
+held me back from writing big posts. I have also created a few org-mode link
+abbreviations such as the one that let me easily link to packages. There are
+also few disadvantages from using this method, which I am hoping to resolve as
+moving forward. One of these disadvantages made me remove the generated website
+from the git repository, now I generate and serve the website through
+~post-receive~ hooks. Once I resolve these, however, I will be adding the =docs=
+directory back to the repository.
diff --git a/content/blog/20210415.org b/content/blog/20210415.org
new file mode 100644
index 0000000..609af88
--- /dev/null
+++ b/content/blog/20210415.org
@@ -0,0 +1,120 @@
+#+TITLE: April 2021 News Post
+#+DATE: <2021-04-15 Thu>
+#+AUTHOR: Cem Keylan
+#+ALIASES[]: /blog/20210415.html
+
+Greetings from the cruellest month of the year! We have some important
+topics this month that I wanted to share with you.
+
+#+TOC: headlines 1 local
+
+** CPT version 6 Release
+:PROPERTIES:
+:CUSTOM_ID: cpt-version-6-release
+:END:
+
+I have released the version 6 of our package manager and did a few bugfix
+releases, which contained a variety of changes made since December. The
+[[https://fossil.carbslinux.org/cpt/log][Changelog]] details them on our new Fossil repository, which I will be talking
+about more on a later section of this post.
+
+As I have mentioned on the [[{{<relref "20210303.org#next-release-for-cpt">}}][previous news post]], I was holding the release for a
+few bugfixes, and documentation. The documentation is complete enough to be
+shipped, but there are still some things to add. The manual pages, and the
+documentation for the user tools, however, are considered complete.
+
+** New rootfs tarball
+:PROPERTIES:
+:CUSTOM_ID: new-rootfs-tarball
+:END:
+
+A new tarball has been released after almost 7 months! This tarball targets the
+=x86_64= architecture, and can be installed following the instructions.
+
+*** Signing Releases
+:PROPERTIES:
+:CUSTOM_ID: signing-releases
+:END:
+
+Releases are now signed with the OpenBSD tool [[https://man.openbsd.org/signify][signify(1)]] instead of GnuPG. There
+are two packages on our repository that provide this tool, {{<pkg "core/otools">}},
+and {{<pkg "extra/signify">}}. Debian-based distributions usually provide it
+under =signify-openbsd=, and other distributions provide it as just =signify=.
+Each release will have a different public key, those can be found on
+[[https://dl.carbslinux.org/keys]]. Since the public keys are so small, I will also
+be embedding the latest release key to the README file of the package
+repository, and the installation manual.
+
+*** The state of i686
+:PROPERTIES:
+:CUSTOM_ID: the-state-of-i686
+:END:
+
+As you may have noticed, I haven't made a release for the =i686= architecture
+this time. I won't be retiring it, but my old laptop, which was the reason I
+initially ported Carbs Linux to the architecture in the first place, has stopped
+working. I won't be retiring it just now, but I also don't see anyone else
+interested in it. If you are interested in taking the maintainership for the
+architecture, you can send a mail to the mailing-list. Otherwise, I will be
+dropping the architecture by the end of June.
+
+** Fossil
+:PROPERTIES:
+:CUSTOM_ID: fossil
+:END:
+
+I have recently been toying around with the alternate version control system,
+[[https://fossil-scm.org][Fossil]]. Since no Carbs Linux News Post is complete without some sort of
+repository migration[fn:1], the canonical repository of the package manager has
+been moved to Fossil on [[https://fossil.carbslinux.org/cpt]]. However, this doesn't
+mean that the mailing-list on Sourcehut will be removed, those will be in place
+until I decide to serve mailing lists on our own server.
+
+As time goes on, I am also planning on switching some other repositories to
+Fossil as well. I will be switching the Documentation repository next, and the
+Package repository when Fossil support is added to the package manager.
+
+*** Fossil support on the package manager
+:PROPERTIES:
+:CUSTOM_ID: fossil-support-on-the-package-manager
+:END:
+
+Right now, the package manager supports Git, Mercurial, and Rsync repositories.
+I do want to add Fossil repository support, however this might take long to
+implement as I will be rewriting the repository backend to simplify and collect
+the operations made by the package manager to manage package repositories.
+
+I'm aiming for a new system that makes it easy and simple to manage repositories
+outside of the package manager's scope as well. These changes can be followed
+from the [[https://fossil.carbslinux.org/cpt/timeline?r=repository-backend][repository-backend]] branch, which as of the time of writing this blog
+post, contains no new check-ins, and specifically the status of Fossil support
+can be tracked from [[https://fossil.carbslinux.org/cpt/tktview?name=b354510bc3][this ticket]].
+
+** Switching back to LibreSSL
+:PROPERTIES:
+:CUSTOM_ID: switching-back-to-libressl
+:END:
+
+This is the 4th time Carbs Linux is switching SSL providers, but I am planning
+on this to be the final change for the foreseeable future. The reason behind
+this change is pragmatism. Even though BearSSL is sufficient enough to run the
+base, some essential packages (such as Python for its SSL module) depended on
+LibreSSL, meaning that using LibreSSL was mandatory if you weren't simply using
+the bare-minimum. Using 2 separate SSL libraries is pointless when you have the
+option to easily use a single one.
+
+** Consistent communication
+:PROPERTIES:
+:CUSTOM_ID: consistent-communication
+:END:
+
+I have decided to be more consistent on these news posts, I will try to make
+these every 15th of the month. I have also recently came back to IRC to be as
+active as possible. At least I can always be reached by mail, if all else fails!
+
+See you on the next post!
+
+** Footnotes
+
+[fn:1] "No mention of openbsd on the internet is complete without a long thread
+about source control migration." -- tedu@ [[https://gameoftrees.org]]
diff --git a/content/blog/20210525.org b/content/blog/20210525.org
new file mode 100644
index 0000000..ecbd070
--- /dev/null
+++ b/content/blog/20210525.org
@@ -0,0 +1,50 @@
+#+TITLE: May 2021 News Post
+#+DATE: 2021-05-25
+#+AUTHOR: Cem Keylan
+#+ALIASES[]: /blog/20210525.html
+
+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
+:PROPERTIES:
+:CUSTOM_ID: fossil-support
+:END:
+
+In the [[{{< relref "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
+:PROPERTIES:
+:CUSTOM_ID: moving-irc-channel
+:END:
+
+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
+:PROPERTIES:
+:CUSTOM_ID: new-i686-release
+:END:
+
+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!
diff --git a/content/blog/20210630.org b/content/blog/20210630.org
new file mode 100644
index 0000000..48611ac
--- /dev/null
+++ b/content/blog/20210630.org
@@ -0,0 +1,15 @@
+#+TITLE: June 2021 News Post
+#+DATE: 2021-06-30
+#+AUTHOR: Cem Keylan
+#+ALIASES[]: /blog/20210630.html
+
+Hello! This month was rather slow for me while I was mostly away for some
+vacation and I had some connectivity issues. I mostly tried to keep the packages
+up to date, and to keep up with the IRC channel as I've had some issues with the
+new logger we are using in the channel. I have very recently returned to home,
+and I'm mostly working on with the next release of the package manager.
+
+Hopefully, next month will be more newsworthy as I will take my time to work on
+the new package repository backend, and document its features.
+
+See you on the next post!
diff --git a/content/blog/20210831.org b/content/blog/20210831.org
new file mode 100644
index 0000000..f39a3c9
--- /dev/null
+++ b/content/blog/20210831.org
@@ -0,0 +1,26 @@
+#+TITLE: August 2021 News Post
+#+DATE: 2021-08-31
+#+AUTHOR: Cem Keylan
+#+DRAFT: true
+
+After a long absence during the summer, I think it's the appropriate time to
+write a new blog post about the changes that arrived to the distribution.
+
+#+TOC: headlines 1 local
+
+* Repository meta file
+
+You might have noticed that most packages now contain a file named =meta=. This
+file contains a small description, license for the package, and the maintainer
+information of the package. A sample meta file looks like the following:
+
+#+begin_example
+description = Carbs Packaging Tools
+license     = MIT
+maintainer  = Cem Keylan <cem@example.com>
+#+end_example
+
+
+* TODO motd file
+* TODO kiss compatibility
+* TODO linux-headers
diff --git a/content/blog/_index.md b/content/blog/_index.md
new file mode 100644
index 0000000..a2797a4
--- /dev/null
+++ b/content/blog/_index.md
@@ -0,0 +1,5 @@
+---
+title: Blog Index
+---
+
+This is the Carbs Linux blog index. You can find every post here.