void-packages
nix
Our great sponsors
void-packages | nix | |
---|---|---|
671 | 366 | |
2,348 | 10,621 | |
2.6% | 7.1% | |
10.0 | 10.0 | |
1 day ago | 1 day ago | |
Shell | C++ | |
GNU General Public License v3.0 or later | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
void-packages
-
Damn Small Linux 2024
I was looking for a lightweight OS to run on old Asus Eee PC 1005 HA, which uses a 32-bit Intel Atom N270 processor. I installed Void Linux (https://voidlinux.org/).
I may give DSL 2024 a try and see how it compares.
- Chimera Linux
- Une nouvelle mise à jour de Systemd permettra à Linux de bénéficier de l'infâme "écran bleu de la mort" de Windows, mais la fonctionnalité a reçu un accueil très mitigé
-
How do I update one of these premade ESP32 boards?
My computer is running Void Linux and it has only a wired network connection. I can hook up my phone for USB tethering if I need to connect to the WiFi of the ESP32. How do I update the software without downloading some shady programs from filesharing site links on my system? I have the Arduino IDE and the esptool.py script installed.
-
Hyphens, minus, and dashes in Debian man pages
Classic "everyone is using the software wrong, but it's the fault of everyone, and not the software".
Some distros like Void seem to patch this out.[1]
From mandoc/mdocml's mandoc_char(7) [2]
In roff(7) documents, the minus sign is normally written as ‘\-’. In manual pages, some style guides recommend to also use ‘\-’ if an ASCII 0x2d “hyphen-minus” output glyph that can be copied and pasted is desired in output modes supporting it, for example in -T utf8 and -T html. But currently, no practically relevant manual page formatter requires that subtlety, so in manual pages, it is sufficient to write plain ‘-’ to represent hyphen, minus, and hyphen-minus.
Which is the common-sense thing to do.
Meanwhile, GNU projects become increasingly less relevant due to obnoxiousness like this.
In general the amount of wankery of "the correct hyphen" is staggering.
[1]: https://man.openbsd.org/mandoc_char
[2]: https://github.com/void-linux/void-packages/blob/20c66829134...
-
OpenSSL 1.1.1 End of Life
> but a year or 2 ago the went back to OpenSSL for some reason which I did not fully understand.
That would be Void Linux [1]. One of the reasons iirc, is PEP 644 [2], in which CPython drops support for LibreSSL due to it not being fully compatible with OpenSSL 1.1.1 APIs.
[1] https://github.com/void-linux/void-packages/issues/20935
-
Installing Debian bookworm without systemd
> I would love if a major distro emerges
Good news for you! You have slackware [0], void [1] and alpine [3], which are widely-used non-systemd distributions with sane scripts. They are well-maintained rolling releases which allow you to use much newer versions of the kernel and packages than your typical ubuntu/debian installs. I don't particularly care about systemd, but these distros are great by themselves!
-
WEBKIT_DISABLE_SANDBOX_THIS_IS_DANGEROUS: Any alternatives?
I'm not a Void Linux user, let alone a maintainer of their packages but it may suffice to simple bump the version at https://github.com/void-linux/void-packages/blob/master/srcpkgs/webkit2gtk/template.
I opened a PR on void-packages.
On the void-packages repo it is stated to not open issues for package updates but to make a PR instead.
nix
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Go + Hypermedia - A Learning Journey (Part 1)
1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity
-
What it was like working for Gitlab
Semi-related, I would recommend to anyone who is a Linux native to try to find some kind of "minimum viable setup" that is really really easy for you to run out of VirtualBox or Parallels or something for this reason. No matter where you go, you know you can have a suite of tools which work just as you want them to there. Being able to tear it down and rebuild it quickly is also a great way to deal with debugging certain kinds of problems of the "it runs/doesn't run on my machine" category.
How you do this is of course up to you. At one end of the spectrum is just relying on your memory. At the other end is using NixOS https://nixos.org/ to get fully reproducible builds anywhere you go. Between these are a vast field of options. I know a guy who maintains an Ansible file set to `host: localhost` which installs everything he wants from that file. For me, I just stick with the latest Ubuntu version and maintain a few shell scripts [1] that install 80% of what I like to have on a new install.
If you like the scientific approach, you can install something like https://atuin.sh/ and do some statistics on what programs you actually run most frequently based on your long term shell history.
-
Cloudflare R2-Backed Nix Binary Cache on Fly.io
See https://github.com/NixOS/hydra/issues/838 for making content-addressed derivations supported by hydra.nixos.org. At that point, we can actually try out the XP feature at scale.
Also see https://github.com/NixOS/nix/issues/8919 for this accepted RFC
Once those things are done, we can get back to merging in the IPFS code.
Now that there is an Nix team and I am on it, there is much, much less of an issue of these experiments being caught in limbo :).
-
The one thing I do not like about the Nix package manager (and a fix for it)
The nix package manager is an awesome package manager for linux and macos, which focuses on declarative packages. This means that you can dump out all the packages you want into a file, and nix will go out and fetch them for you.
- NixOS: Declarative Builds and Deployments
-
Beginners Intro to Trunk Based Development
Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).
-
Practical Guide to Trunk Based Development
There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:
-
How I use Nix in my Elm projects
Nix is a tool that allows you to make reproducible development environments. I've started using it in all my Elm side projects and I've had a good experience with it thus far. To pique your curiosity I just wanted to share my simple setup that has been working quite well for me.
-
Shopware Changes since the 6.0 Dev Training Videos
The latter one is based on nix OS using Symfony flex recipes and PHP packagist composer. The flex devenv should work cross-platform on Linux, Windows, and Mac. "The main difference to other tools like Docker or a VM is that it neither uses containerization nor virtualization techniques. Instead, the services run natively on your machine."
What are some alternatives?
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
ungoogled-chromium - Google Chromium, sans integration with Google
gentoo - Official Gentoo ebuild repository
sway - i3-compatible Wayland compositor
xdeb - XDEB - Convert deb (Debian) packages to xbps (Void Linux)
flatpak - Linux application sandboxing and distribution framework
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
linux-surface - Linux Kernel for Surface Devices
picom - A lightweight compositor for X11
guix - Read-only mirror of GNU Guix — pull requests are ignored, see https://guix.gnu.org/en/manual/en/guix.html#Submitting-Patches instead