Live data from Hacker News

Void Linux: Into the Void

michaelwashere.net

71–80 of 104 posts

Re: Void Linux: Into the Void

#71

"Because of this, xbps-src is in fact not a binary, it is a collection of very intricate shell scripts that use standard tooling available on almost any Linux distribution to bootstrap a compiler, build chroot, and XBPS itself." When he stepped away from NetBSD, I remember reading that it was because he wanted to work on a package manager. It might be that the entire raison d'etre for Void Linux is a package manager…

Gobolinux is also mostly powered by shell script (i think you may find the odd python and compiled code in there for performance reasons).

Re: Void Linux: Into the Void

#72
post #37
post #28

Earlier quoted context omitted.

Isn't devops basically an infrastructure engineering, which if anything, is as anti-systemd as it gets. I guess people think of devops as something different then.

Some people use "devops" as a derogatory term for developers copy-pasting stuff to the terminal. Certain in-terms tend to acquire ironical undertones quite quickly, such as "agile" now meaning certified scrum masters(tm) doing half hour standups.

For me devops is summed up thus:

http://www.commitstrip.com/en/2015/07/08/true-story-fixing-a...

Re: Void Linux: Into the Void

#73
post #57

Earlier quoted context omitted.

I'm having a .... not fun time updating darch to the latest version. Does your makefile still require git, or can I kill that code?

You can remove the git stuff, as long as you are not building containerd and runc as well. What issues are you running into? The AUR and VoidLinux package don't have an issue. Skype (paul.knopf1) me?

Why does a go get pull in docker and everything else?

I'm trying to clean up the Void package to make it more maintainable.

Re: Void Linux: Into the Void

#74
post #57

Earlier quoted context omitted.

You can remove the git stuff, as long as you are not building containerd and runc as well. What issues are you running into? The AUR and VoidLinux package don't have an issue. Skype (paul.knopf1) me?

Why does a go get pull in docker and everything else? I'm trying to clean up the Void package to make it more maintainable.

Darch isn't "go get"-able. Things need to be vendored and you'll need a certain version of containerd and runc (which isn't "go get"-able either).

Are you having a problem with the Void package script? The go build template for Void is very naive, I wouldn't use it. It uses symlinks which doesnt place nice with vendoring tools. Things will be a lot smoother when vgo is done and their template is updated accordingly.

Re: Void Linux: Into the Void

#75

I ran the musl libc version of Void Linux for a while on one of my laptops but ran into a lot of problems and buggy behavior. If you are going to use Void Linux I would strongly recommend not picking the musl version unless you are specifically interested in improving musl support by filing and/or fixing bugs.

Do wonder how much of that was from code having adopted GNU-isms...

honestly not that much since adopting a GNU-ism or Glibc-ism will in most case result in errors at compile-time.

Re: Void Linux: Into the Void

#77

Why would one use Void instead of NixOS or another Nix-based distro?

If you're into programming in C, and like simplicity, you might find more likeminded people there, similar to OpenBSD. Nix is more popular among functional programmers.

Nix is for everybody; I don't do functional programming but I still use Nix for everything. If OpenBSD is simple, or C is simple, and Void is also simple, then it sounds like I should not bother trying out Void.

Re: Void Linux: Into the Void

#78
post #74

Earlier quoted context omitted.

Why does a go get pull in docker and everything else? I'm trying to clean up the Void package to make it more maintainable.

Darch isn't "go get"-able. Things need to be vendored and you'll need a certain version of containerd and runc (which isn't "go get"-able either). Are you having a problem with the Void package script? The go build template for Void is very naive, I wouldn't use it. It uses symlinks which doesnt place nice with vendoring tools. Things will be a lot smoother when vgo is done and their template is updated accordingly.

Except that the makefile really depends on submodule updates and other mechanisms that require a git clone (hard on the build servers) instead of a tarball that can be cached and checksummed.

Re: Void Linux: Into the Void

#79

"after all the package manager is really just keeping a database of files and unpacking archives onto the disk." err..... what

What what? That's more or less what a package manager does; take archives ("packages"), unpack them into the system ("install"), and then keep a database of what archives are unpacked and what files each one owns. In practice there's a lot added to that (pulling the archives from a central repo, dependency resolution, searching, managing config files...), but the simple case is barely more than tar.

Re: Void Linux: Into the Void

#80

"Because of this, xbps-src is in fact not a binary, it is a collection of very intricate shell scripts that use standard tooling available on almost any Linux distribution to bootstrap a compiler, build chroot, and XBPS itself." When he stepped away from NetBSD, I remember reading that it was because he wanted to work on a package manager. It might be that the entire raison d'etre for Void Linux is a package manager…

> One project I have had on the list for many years is to build Linux on BSD. Could it be done? Has it been tried?

How do you mean? Compiling the Linux kernel on a BSD machine? Using GNU on BSD (if so, the answer is yes; see Debian GNU/kFreeBSD)? Linux kernel with BSD userland?

Post reply on HN