Official Packages and Directory #899

Closed
opened 2023-09-21 19:27:05 +00:00 by vyzo · 9 comments
vyzo commented 2023-09-21 19:27:05 +00:00 (Migrated from github.com)

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:

  • we only list high quality, known maintained packages
  • we move the mysql driver out of tree and into the clan namespace
  • we adopt @fare's high quality packages and move them to mighty-gerbils
  • we have an sexp format for package listing, documented and extensible
  • gxpkg by default should pull from the official package directory, but also accept an option for a user specified directory so that we can grow a decentralized communal codebase.
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: - we only list high quality, known maintained packages - we move the mysql driver out of tree and into the clan namespace - we adopt @fare's high quality packages and move them to mighty-gerbils - we have an sexp format for package listing, documented and extensible - gxpkg by default should pull from the official package directory, but also accept an option for a user specified directory so that we can grow a decentralized communal codebase.
vyzo commented 2023-09-21 20:15:41 +00:00 (Migrated from github.com)

And the kicker: have a user list stored in .gerbil for 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

And the kicker: have a user list stored in `.gerbil` for 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
vyzo commented 2023-09-21 22:58:05 +00:00 (Migrated from github.com)

Following discussion, consensus is to move foreign packages (yaml, leveldb, lmdb) out of the main tree as official packages, still highlighted in the guide.

Following discussion, consensus is to move foreign packages (yaml, leveldb, lmdb) out of the main tree as official packages, still highlighted in the guide.
afternoon commented 2023-09-22 10:53:33 +00:00 (Migrated from github.com)

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.

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.
vyzo commented 2023-09-22 11:23:35 +00:00 (Migrated from github.com)

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.

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.
vyzo commented 2023-09-22 11:42:37 +00:00 (Migrated from github.com)

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.

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.
vyzo commented 2023-09-23 14:24:53 +00:00 (Migrated from github.com)

The mighty gerbils directory is live: https://github.com/mighty-gerbils/gerbil-directory
Working on the gxpkg side of things, pr forthcoming.

The mighty gerbils directory is live: https://github.com/mighty-gerbils/gerbil-directory Working on the gxpkg side of things, pr forthcoming.
vyzo commented 2023-09-23 20:00:59 +00:00 (Migrated from github.com)

And #916 implements the requisite client side.

And #916 implements the requisite client side.
vyzo commented 2023-09-23 20:04:39 +00:00 (Migrated from github.com)

The foreign dependency move was done in #914

The foreign dependency move was done in #914
vyzo commented 2023-09-24 09:24:13 +00:00 (Migrated from github.com)

Build isolation and documentation here:

Build isolation and documentation here: - #918 - #919
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mighty-gerbils/gerbil#899
No description provided.