From 08c5bd21fa02e1b30fe2e4c194d9c615a4daf2c6 Mon Sep 17 00:00:00 2001
From: Cem Keylan <cem@ckyln.com>
Date: Tue, 31 Aug 2021 01:13:15 +0300
Subject: website: switch to hugo

---
 content/blog/20200617.org | 89 +++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 89 insertions(+)
 create mode 100644 content/blog/20200617.org

(limited to 'content/blog/20200617.org')

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.
-- 
cgit v1.2.3