Waterfall development was coined in a paper describing how it is bad.

That's not how he was using the phrase.

Doesn't say it's 3x3.

Our initial author, and the primary author of xbps, came directly from the NetBSD community.

Installed on an old Thinkpad X61s from the xfce4 live .iso (< 600Mb) dd'ed to a usb stick. Boots into an xfce live graphical session with network-manager recognising the Atheros wifi card. Minimal install - xfce 4.12 plus Web browser and image viewer (1.5Gb on hard drive).

Ran the installer script from a terminal in the live session - result is an ncurses dialogue that walks you through the steps. Disk already partitioned and skipped the network set-up stage and selected install from local. Rebooted into (graphical, xfce4) installed system in a few minutes. Network manager up and running, needed to log-in to local wifi again.

Probably because I skipped the network stage in the installer, I needed to set a repository for updates.

     echo 'repository=http://repo.voidlinux.eu/current/' \ >  
     /etc/xbps.d/00-repository-main.conf

(somewhat reminiscent of OpenBSD's 6.2 new installurl)

Now installing some applications. LibreOffice is version 6 'fresh'. A bit like OpenBSD, installing Libreoffice brings a metric tonne of dependencies.

Edit: you need to install alsa to get sound

     xbps-install alsa-utils

gets you basic sound functionality. The 'stem matches package name' logic is very reminiscent of OpenBSD pkg_add (I've never used NetBSD).

It looks like you've already figured out some things like sound, wifi, and xbps, but: I found the following guide helpful in complementing the man pages:

http://www.troubleshooters.com/linux/void/voidtips.htm

More articles on Void from the same author, including an install guide:

http://www.troubleshooters.com/linux/void/index.htm

Thanks.

I worked out that root defaults to /bin/sh before reading the voidtips page above. Also worth mentioning here that Firefox-esr (52) is installed by default from the xfce4 live iso. Firefox release (59) is also available as is Chromium (65). Some font-puggling is needed (fontconfig stuff) to get sub-pixel rendering.

In all, quite nice. I'll see how long it takes me to break this.

Question - is there any reason your project can only be used on x86_64? I can't readily find documentation about godarch that suggests it even requires 64bit hardware.

The base docker images (https://github.com/godarch/distributions) only supports x86_64. Docker images have support for having multiple embedded rootfs tarballs for multiple platforms, but it gets complicated. Maybe in the future.

Also, you have to build your recipes on the same target arch that you are going to deploy to. Irrelevant to your question, but something to note.

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.

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.

Yeah, when I added the package, I told them the next version will not require vendoring and can be built without git. The next version will do this.

Why did you leave Clojure?

Clojure weenies on IRC. To be fair, the Go weenies aren't much better. If you like hanging out on IRC so that you can emotionally abuse newbies, ask yourself what you're doing with your life.

Fascinating, so it was purely a communal decision.