Getting rid of *.la files once and for all
Posted: 2024-09-27 Filed under: system | Tags: CRUX, la, la files, lib 14 CommentsCRUX does not remove *.la files by default. I try to make my ports clean these up, but there are many others that still ship them. I have run into pretty silly problems because of them, so I decided to do something about it.
Read the rest of this entry »
VirtualBox on a CRUX host
Posted: 2024-05-12 Filed under: system | Tags: CRUX, virtualbox Leave a commentFor virtualization, I use VirtualBox, installed from the All distributions binary package provided by upstream (*.run). Since CRUX is a bit of an esoteric distribution, startup stuff and building of kernel modules does not happen automatically. Therefore, calling certain scripts should be done manually.
Read the rest of this entry »
Traditional names of network devices
Posted: 2024-02-04 Filed under: network, system | Tags: adapter, CRUX, eth0, grub, lilo, network, wlan0 Leave a commentMoving from Slackware to CRUX, I noticed that my network devices have weird names, such as enp4s0. What happened to the good old eth0? It did not bother me much at first, but… For example, I have a firewall script, where I specify adapter names, and it is a bit annoying to always check for the specific one, depending on the computer I am working on.
Read the rest of this entry »
r4-modules repo added to portdb
Posted: 2024-01-21 Filed under: ports, system | Tags: cran2crux, CRUX, modules, portdb, ports, R, r-modules, r4-modules Leave a commentMy collection of ports building R modules has been just added to the portdb section of CRUX, as r4-modules. At the moment, there are 374 entries, mostly bioinformatics-oriented. The ports themselves are hosted at my crux-ports GitHub.
I have been using the repo for about a month, but thought that others may benefit from it, too. So, here it is.
Read the rest of this entry »
cran2crux: ports for R modules
Posted: 2023-12-27 Filed under: ports, system | Tags: CRAN, CRUX, portdb, ports, R Leave a commentI use R in my work and I wanted to find a way to easily create CRUX ports for system-wide installation of its modules. Having them managed by the distro’s packaging system has its advantages: I can check them with revdep or use custom settings at build time. However, I did not find a ready solution, so I wrote a tool myself, called cran2crux (for detailed info, check it’s page). The cran2crux script automatically generates CRUX port(s) for R modules available from CRAN. On my TODO list is making it work with Bioconductor, as well.
Read the rest of this entry »
Slackalaxy 