2 ms·
> 6. Produced tarball releases have fewer build dependencies than those produced by competitors. <- Was not aware of this. Let's take his word for it. I believ
by jcranmer 6y ago
> 6. Produced tarball releases have fewer build dependencies than those produced by competitors. <- Was not aware of this. Let's take his word for it.
I believe the intent is to say "you need autotools to build the tarball, but the tarball doesn't need autotools, just regular POSIX tools", which is a jab at systems like cmake where you need cmake to do the configuration at tarball time.
Except, well, the introduction of DVCSes like git has shifted a lot of software away from "build from tarball" to "build from VCS checkout," so the value is rather lesser. Indeed, you can turn it around and claim that this is an antifeature: it takes more work to build a tarball and do VCS checkout than not.
- derefr 6y agoDevelopers build stuff from VCS checkouts. But the package managers and ports systems that regular users rely upon, still use tarball releases, not VCS checkouts, as their upstreams. For example: Homebrew. If you tell Homebrew to --build-from-source, it'll pull down a release tarball from its release URL; unpack it; set up the shell environment just so; and then run the same very same ./configure script the upstream generated with Autotools. It'd actually be kind of a problematic bootstrapping problem if that ./configure script did require Autotools to run, as there's no real legal way for (proprietary) macOS to ship (GNU, GPLv3) Autotools. And that's much the same problem many other proprietary UNIXes were in, back when: wanting to support "standard" tooling, but being too wary of this new "copyleft" thing to be willing to ship any GPLed software as part of their OS. Thus, the broadest industry support came out for the tooling that doesn't force the upstream's tooling's licensing choices on the downstream. (Ironically, that tooling happened to be from GNU, the precise people whose software they were trying to avoid shipping.)
- einpoklum 6y ago> "build from VCS checkout," so the value is rather lesser. But why does building from VCS checkout make any difference? If anything, there are _more_ requirements that way, since a tarball release can possibly be made to rely on less (e.g. generating ad-hoc install scripts).