aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCem Keylan <cem@ckyln.com>2021-10-25 16:05:10 +0200
committerCem Keylan <cem@ckyln.com>2021-10-25 16:05:10 +0200
commit777acabb0bd21d87fa590b7404a4847bd02c12d4 (patch)
tree36e07fa021738e59ee59e695da13124ab07cc921
parenta3d32ffed9bb185072c96541fd273faa26d70e59 (diff)
downloadwebsite-777acabb0bd21d87fa590b7404a4847bd02c12d4.tar.gz
October 2021: add custom ids
-rw-r--r--content/blog/20211025.org19
1 files changed, 18 insertions, 1 deletions
diff --git a/content/blog/20211025.org b/content/blog/20211025.org
index 7ccda62..af52a11 100644
--- a/content/blog/20211025.org
+++ b/content/blog/20211025.org
@@ -1,7 +1,6 @@
#+TITLE: October 2021 News Post
#+DATE: 2021-10-25
#+AUTHOR: Cem Keylan
-#+DRAFT: true
After a long absence during the summer and working my way through moving to
Berlin, I think it's the appropriate time to write a new blog post about the
@@ -12,6 +11,9 @@ this post for so long, there are quite a numerous details to be discussed.
#+TOC: headlines 1 local
* Repository meta file
+:PROPERTIES:
+:CUSTOM_ID: repository-meta-file
+:END:
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
@@ -56,6 +58,9 @@ documentation. Also see =cpt-search(1)= for more information on the flags and
their behaviours.
* Blake3 checksums
+:PROPERTIES:
+:CUSTOM_ID: blake3-checksums
+:END:
The package manager now uses BLAKE3 to generate checksums, however this change
is backwards compatible, and does not break any old packages that are lying
@@ -64,6 +69,9 @@ can generate the checksums using ~cpt-checksum -s~, which is what I'm using the
generate the checksums for the =cpt= package itself.
* Message of the Day files
+:PROPERTIES:
+:CUSTOM_ID: message-of-the-day-files
+:END:
With the release of the version =6.1.0= of CPT, I have added a =MOTD= file for
displaying updates and important information from the repository. This file is a
@@ -71,6 +79,9 @@ simple plaintext file that should be present on the root of the repository, and
it is printed to the standard output during the =cpt-update= command.
* Adding the core repository to the tarball
+:PROPERTIES:
+:CUSTOM_ID: adding-the-core-repository-to-the-tarball
+:END:
I am thinking of adding a copy of the =core= repository to the release tarballs.
By adding it, it will be a good incentive to remove the =git= package from the
@@ -78,6 +89,9 @@ tarball, and let the user choose which repository backend they want to install
(=git/fossil/rsync=) instead of enforcing =git=.
* Packaging Linux Kernel headers
+:PROPERTIES:
+:CUSTOM_ID: packaging-linux-kernel-headers
+:END:
The kernel header files are now packaged from a separate source tarball that
/only/ contains the kernel headers so that the downloads are much smaller. For
@@ -89,6 +103,9 @@ You can also fork the package and install LTS headers that are also provided by
this repository, if they better fit your needs.
* Website Update
+:PROPERTIES:
+:CUSTOM_ID: website-update
+:END:
No blog post is complete without me butchering this website, trying to shove it
into a different static site generation software, breaking lots of links in the