Nick Logan

Using `--exclude=python2-config` is explicitly ignoring python2-config, otherwise there would be a dependency error. On that same note one can also do `--exclude=python2.7`.

@bazzaar thats a bit odd because `zef install Inline::Python` should be finding and installing `Distribution::Builder::MakeFromJSON` -- at least it does for me locally, and it shows up in Xliff's output...

@bazzaar Xliff is showing the expected behavior, and the same behavior I'm witnessing. I can only assume you/rakudo-star has some old version of `Distribution::Builder::MakeFromJSON` installed and thus it wasn't needed.

zef has [special-cased](https://github.com/ugexe/zef/commit/cb648e59171dd56b3b7064639758c33bfb8bd49a) 'MakeFromJSON' for the time being. Some time in the near future you should be able to merge this with little fallout.

@niner how shall we handle this in install-dist.pl? Do we do `my $builder-class = first { *.so }, (try require ::("$name")), (try require ::("Distribution::Builder::$name")` with a deprecation warning, or should...

install-dist.p6 will handle a full namespace or the original implied prefix version as of https://github.com/rakudo/rakudo/commit/0249afc26fbac525969ef19e52da33cd794ba275 and the spec updated as of https://github.com/perl6/specs/commit/26266b1bc69cd15b58ab03338af7f3938052b666 to reflect that using the full namespace is...

That is not using `zef:ver` like you may think, which is evident by the message: `http://ecosystem-api.p6c.org/projects.json` which in v0.4.2 would read: `http://ecosystem-api.p6c.org/projects1.json` It is possible to have `zef:ver` installed but...

> This is exactly what I would like to see when installing a package. I don't necessarily need to know what actual test is running, but a single test file...

As far as how things would consume this I would expect a simple, single endpoint (or an endpoint-per-topic) that contains some number of messages. Tooling that consumes this then does...

I’m pretty sure Distribution is both documented and specced: $dist.content('resources/config.txt').open(:bin).slurp.decode.chars;