Added: manage-slackware-packages-2026 [en,it]release_04052026-2044content-refactoring

1 files changed, 5 insertions, 8 deletions

diff --git a/content/en/articles/manage-slackware-packages-2026/index.md b/content/en/articles/manage-slackware-packages-2026/index.md
index 294a617..ac31ba5 100644
--- a/content/en/articles/manage-slackware-packages-2026/index.md
+++ b/content/en/articles/manage-slackware-packages-2026/index.md
@@ -1,28 +1,25 @@
 +++
 title = "Managing packages in Slackware in 2026."
-
 date = "2026-05-04"
 type = "tech"
-draft = true
 image = "/uppies/2026/05/ascii-1920x1080.png"
 excerpt = "My updated workflow for managing packages in Slackware64 current."
-
 tags = ["linux", "git"]
 categories = ["Code", "DIY"]
 
 +++
-These days, I only write articles about the various workflows that I have implemented and improved over time to manage various aspects of my day at the computer: :sunglasses:
+These days, I only write articles about the various workflows that I have implemented and improved over time to manage various aspects of my day at the computer :sunglasses:
 
 Today, it's about the workflow I follow to manage my Slackware packages. You can find the repository at the top of the menu, or by clicking the button below:
 
-{{< Actions url="https://packages.danix.xyz" desc="packages.danix.xyz" use="site" caption="Il mio repository di pacchetti per Slackware" >}}
+{{< Actions url="https://packages.danix.xyz" desc="packages.danix.xyz" use="site" caption="my Slackware Packages Repository" >}}
 
 ## My Repos
 
 Most of the scripts I write follow the standards of [slackbuilds.org](https://slackbuilds.org/guidelines/), except where it is impossible to apply them. I manage the slackbuild repositories on GitHub, where I maintain:
 
-- a repository of [pacchetti personali](https://github.com/danixland/my-slackbuilds) (packages that are not on SBo or that have specific compilation flags, sources from git repositories, etc.)
-- a repository of [pacchetti incentrati sulla cybersecurity](https://github.com/danixland/Slackware-Pentesting-Suite), with some packages published by me or others on SBo, while others are only on the personal repo.
+- a repository of [personal packages](https://github.com/danixland/my-slackbuilds) (packages that are not on SBo or that have specific compilation flags, sources from git repositories, etc.)
+- a repository of [packages revolving around cybersecurity](https://github.com/danixland/Slackware-Pentesting-Suite), with some packages published by me or others on SBo, while others are only on the personal repo.
 
 ## Compiling Packages
 
@@ -33,7 +30,7 @@ I only use the virtual machine with slackware *-stable* to test the compilation
 The machine with *-current*, on the other hand, is the one I use most often, as it is the one that generates the packages that I also use on my physical computer; the same packages that I then publish on **packages**.
 
 {{< callout type="warning" >}}
-The packages in [mio repository](https://packages.danix.xyz) are all compiled for slackware64-current and will not work on slackware64-stable.
+All the packages in [my repository](https://packages.danix.xyz) are compiled for slackware64-current and will not work on slackware64-stable.
 {{< /callout >}}
 
 To compile the packages, I rely on [slackrepo](https://github.com/aclemons/slackrepo), a program originally written by [David Spencer](https://github.com/idlemoor/) (aka idlemoor), and whose development has recently been taken up by [Andrew Clemons](https://github.com/aclemons) (aka aclemons).