Waterfall development was coined in a paper describing how it is bad.
Doesn't say it's 3x3.
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.
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.
Our initial author, and the primary author of xbps, came directly from the NetBSD community.
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?
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.
Fascinating, so it was purely a communal decision.
Why did you leave Clojure?
Waterfall development was coined in a paper describing how it is bad.
Doesn't say it's 3x3.
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.
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.
Our initial author, and the primary author of xbps, came directly from the NetBSD community.
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?
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.
Fascinating, so it was purely a communal decision.
Why did you leave Clojure?