Official Packages and Directory #899
Labels
No labels
UX
active development
backlog
blocker
bootstrap
bounty
bug
dependencies
discussion
documentation
duplicate
enhancement
flaky test
help wanted
invalid
javascript
question
release
tendentious
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mighty-gerbils/gerbil#899
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, gxkpg uses my personal gerbil-directory thing for package search, parsing the markdown... yikes
Not only this is not a general solution, a lot of these packages have bitrotted.
We want to make an official package directory in mighty-gerbils, such that:
And the kicker: have a user list stored in
.gerbilfor package directories, and easy way to add remove directories from that list.So power users can maintain their own package directories and easily share it with each other.
cc @ober @drewc @belmarca
Following discussion, consensus is to move foreign packages (yaml, leveldb, lmdb) out of the main tree as official packages, still highlighted in the guide.
Package repositories seem to be a tough area in Scheme. Each implementation has their own, which splits the capacity available for creating great libraries and makes it harder to gain critical mass.
I'm not sure what the solution is here, but one thing that could be interesting would be to integrate somehow with Akku, or other repos, so that I can pull great Scheme code agnostic of where it has been uploaded.
This presents compatibility challenges, not to mention supply-chain risk, but the win would be increased productivity when using Gerbil for a project.
Yes, we are consdiering doing this.
It won't be ready for v0.18, but we do want to add to gxpkg the ability to pull from known scheme package repositories.
The difficulty is how to compile that code we pull, but it is not insurmountable.
Follow up in #903 so that we keep track of it and don't forget; contributions always welcome if you want it to happen faster, but be advised that we are near code freeze for v0.18-rc1.
The mighty gerbils directory is live: https://github.com/mighty-gerbils/gerbil-directory
Working on the gxpkg side of things, pr forthcoming.
And #916 implements the requisite client side.
The foreign dependency move was done in #914
Build isolation and documentation here: