vyzo

You need to somehow define these identifiers, perhaps with an `extern`. You can have a custom prelude for each dialect, which provides the necessary symbols.

Yeah, the documentation is not there for the expander yet. It returns a syntax object containing the source code that was expanded. You can process the syntax object with the...

If you need syntax-case at runtime, you can import ``.

One can call that a bug, gxpkg should indeed check for executable bit and give a better error message if it is not.

well technically, if it's not url encoded it's not a a valid url!

Well, the Makefile is redundant -- the package assumes a build script which builds with the standard build tool (`:std/make`). But this is a great proposal overall, I would very...

I am opposed to using Makefiles as the build vehicle. The package manager already utilizes the build script which covers all basic functionality for building gerbil (and properly namespaced gambit)...

Now, with regards to the basic functionality of search and metadata. Firstly, we need additional metadata in packages. This can be simply done by having a `metadata:` field in the...

gxpkg can also work with a shell script, provided it supports a couple of meta-commands (`deps` and `compile`). But it won't be able to clean packages without the `spec` meta-command,...

I believe that tightly integrating the module system with versioning is a mistake -- you get versioning hell, and npm and worse. I believe by default the system should build...