Added: article slackware-templates-for-packages [en,it]release_12052026-1149

1 files changed, 9 insertions, 11 deletions

diff --git a/content/en/articles/slackware-templates-for-packages/index.md b/content/en/articles/slackware-templates-for-packages/index.md
index 04c001a..b706187 100644
--- a/content/en/articles/slackware-templates-for-packages/index.md
+++ b/content/en/articles/slackware-templates-for-packages/index.md
@@ -1,13 +1,11 @@
 +++
 title = "Slackware Templates for Packages"
-
 author = "Danilo M."
 type = "tech"
 date = "2026-05-11T18:51:37+02:00"
 draft = true
 excerpt = "slackpkg and dependency management in Slackware."
-
-image = ""
+image = "/uppies/2026/05/water-02-1024x768.jpg"
 tags = ["linux", "howto", "do it yourself"]
 categories = ["Code", "DIY"]
 
@@ -22,7 +20,7 @@ The same applies to package compilation; since it doesn't manage dependencies, y
 
 To solve this last problem, there are software programs like [sbopkg](https://www.sbopkg.org/) that allow you to generate compilation queues to compile the packages needed for the software in the correct order.
 
-One step further than sbopkg is **slackrepo**, software that I have already talked about in my [articolo sulla gestione dei pacchetti nel 2026](../manage-slackware-packages-2026/), as it also allows you to compile the packages in the correct order with respect to the dependencies of each individual program, but in addition, it installs the already compiled dependencies one by one and then removes them once the compilation of the software that required them is finished.
+One step further than sbopkg is **slackrepo**, software that I have already talked about in my [article about managing packages in slackware in 2026](../manage-slackware-packages-2026/), as it also allows you to compile the packages in the correct order with respect to the dependencies of each individual program, but in addition, it installs the already compiled dependencies one by one and then removes them once the compilation of the software that required them is finished.
 
 The most interesting feature of slackrepo, however, is the ability to queue "hooks" to the execution of the program, i.e., to execute code that is not part of slackrepo to extend its functionality. In particular, in my setup, I use several hooks:
 
@@ -31,11 +29,11 @@ The most interesting feature of slackrepo, however, is the ability to queue "hoo
 - I generate the .template files for those software programs that have one or more dependencies.
 - I upload the files to the repository using rsync.
 
-{{< actions url="https://packages.danix.xyz" desc="I miei pacchetti" use="site" caption="Il mio repository di pacchetti per slackware64-current" >}}
+{{< actions url="https://packages.danix.xyz" desc="my packages" use="site" caption="My packages repository for slackware64-current" >}}
 
 ### hook "git fetch"
 
-This hook takes care of updating the local repository by cloning Ponce's git (it's on *-current*), then it performs the rebase and stops the execution if there are any conflicts, so I know if any of my personal packages conflict with SBo's. In case of conflicts, I can resolve them by deleting my package or the official one, depending on the situation.
+This hook takes care of updating the local repository by cloning Ponce's git (I'm on *-current*), then it performs the rebase and stops the execution if there are any conflicts, so I know if any of my personal packages conflict with SBo's. In case of conflicts, I can resolve them by deleting my package or the official one, depending on the situation.
 
 ```bash
 function danix_gitfetch_hook
@@ -74,7 +72,7 @@ function danix_gitfetch_hook
 
 ### hook "gen web files"
 
-This hook takes care of launching my script `gen_web_hook.sh` (visible on [mio git](https://git.danix.xyz/pkgs-html-structure/tree/gen_web_hook.sh)) to generate the HTML files that will then be uploaded online to the package repository and that are used for viewing the repository online.
+This hook takes care of launching my script `gen_web_hook.sh` (visible on [my git](https://git.danix.xyz/pkgs-html-structure/tree/gen_web_hook.sh)) to generate the HTML files that will then be uploaded online to the package repository and that are used for viewing the repository online.
 
 ```bash
 function gen_web_hook
@@ -89,7 +87,7 @@ function gen_web_hook
 }
 ```
 
-{{< actions url="https://git.danix.xyz" desc="Il mio repository git" use="repo" caption="Dai un'occhiata al mio codice sul repo git." >}}
+{{< actions url="https://git.danix.xyz" desc="my git repository" use="repo" caption="Have a look at my code on my git repo." >}}
 
 ### hook "template generator"
 
@@ -170,10 +168,10 @@ function rsync_push_hook
 
 ## The .template files and slackpkg
 
-At the end of the compilation of software that has some dependencies, in my repository, the file `<nome_pacchetto>.template` will be generated, which I can copy into `/etc/slackpkg/templates` and call with:
+At the end of the compilation of software that has some dependencies, in my repository, the file `<package_name>.template` will be generated, which I can copy into `/etc/slackpkg/templates` and call with:
 
 ```bash
-slackpkg install-template nome_pacchetto
+slackpkg install-template package_name
 ```
 
 and slackpkg will automatically prompt me to install all the dependencies listed in the template, effectively simplifying dependency management.
@@ -190,4 +188,4 @@ waybar
 
 I hope this article can be useful to someone, even if only as a starting point to simplify things a bit :wink:
 
-{{< actions url="/it/is/here/" desc="Scrivimi" use="site" caption="Se hai dei commenti, lasciami pure un messaggio" >}}
\ No newline at end of file
+{{< actions url="/it/is/here/" desc="Contact me" use="site" caption="If you have any comments, leave a message." >}}
\ No newline at end of file