Max Howell

Really we should build them and then have pkgx ignore them by default. If they don’t build then we discard that release because we don't care much.

The new `bkpyvenv` supports this to some extent. Hard to be sure though since I'm not sure from the report if the issue is that two virtual-environments are needed or...

we could probably deprecate `props` and use the new per array node prop in general since adding files to a build directory is asking for issues like @magnusviri’s

we could allow the `prop:` node to take a filename

Yes this is certainly needed. Doing it for build deps only is easier than for runtime (it makes the graph calculation significantly more complex, potentially unsolvable even, which is part...

probs we should remove the top-level fixture. The above example though artificial would be better as inline fixtures per array node imo. In the case where you want fixtures that...

`+brewing` is broken at some level and needs revisiting. In general it should be transparent: * any bug is either exposing general relocatability issues; or * should be transparent since...

k I think I see the problem. This only happens on systems without `/usr/share/dict/words`. Can be avoided if you pass the pkgname as an arg for now.

k the referenced package is not building from source, it is using a pre-built (but freely distributable) vendor built package. Unless I'm mistaken? We do want to support this. We...

linux pkgx has some “pre requisite” deps, the main one is glibc >=23. We aim to provide these ourselves eventually, but currently that's the state of it. Swift for Ubuntu...