Max Howell
Max Howell
Interested in how it effects startup time. Also we clearly need to pkg `upx` And would love to get into Debian, but yeah, since they don't have deno yet it...
found some further info here: https://github.com/denoland/deno/issues/9198 So indeed, stripping deno will lead to smaller compiled binaries. I worry that it may result in non functional binaries. Defaulting it is a...
the search box will search for programs (binaries) that pkgs provide
Yeah totes want it. We’re having trouble building 1.41 over at the pantry, and couldn't bump to 1.40 due to deprecated API with no replacements at that time. Once 1.41...
FYI if you strip deno first it results in smaller binaries too.
So main remaining issue is libpkgx uses `Deno.run` which is deprecated but is necessary to build libpkgx with `dnt` so we can publish to npm because `Deno.Command` is not available...
This is good, but will not merge with the unnecessary prettier changes to the YAML. I probs will just fix the PR myself or squash and then fix. edit: specifically...
Yeah we're leaning towards mash scripts for now here. I think for pkgx v2 the install command will become its own package built on `pkgx` tech, as we intend for...
`pkgx` by itself lists the active environment and used to say something if there is none. Certainly listing `--help` makes sense though even though it's convention, I don't consider it...
I have patches to use an sqlite cache for pkg resolution which is as yet not added to any release because the mechanism by which we use sqlite is dodgy....