Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pkg request megathread #1

Open
5 tasks
mxcl opened this issue Feb 3, 2025 · 7 comments
Open
5 tasks

pkg request megathread #1

mxcl opened this issue Feb 3, 2025 · 7 comments

Comments

@mxcl mxcl pinned this issue Feb 3, 2025
@jhheider
Copy link

jhheider commented Feb 3, 2025

could definitely move https://github.com/elizaOS/eliza here. i suspect it'll remain a moving target for some time.

@mxcl
Copy link
Member Author

mxcl commented Feb 3, 2025

Does feel more like this kind of thing. I suggested mash before but I think mash is: novel scripts on top of stuff in pkgx.

I think my criteria for what goes in pkgx is moving towards:

  • provides a CLI tool that is the documented way to engage with it (thus llama.cpp was not suitable until recently)
    • or is a versioned library
  • versioned

I will be pruning mash and pkgx at some point to avoid the duplication.

@jhheider
Copy link

jhheider commented Feb 3, 2025

this is the way. llama.cpp has insanely frequent builds more suitable to pkgo, and agpt.co moved to a "platform" form some time ago that resisted traditional packaging.

(and llama.cpp confuses our versioning logic, since it hits our carve-out for calver in a weird way.)

@mxcl
Copy link
Member Author

mxcl commented Feb 3, 2025

vim also has insanely frequent version bumps, but I don't see us removing that from pkgx.

@jhheider
Copy link

jhheider commented Feb 3, 2025

i can dream, can't i?

@mxcl
Copy link
Member Author

mxcl commented Feb 3, 2025

I do wonder what the vim project exactly expects packagers and users to do.

@jhheider
Copy link

jhheider commented Feb 3, 2025

I do wonder what the vim project exactly expects packagers and users to do.

we're straying off topic, but it looks like debian does the normal debian thing:

  • freeze stable (9.0.1378, 3/4/23)
  • update unstable sometimes (9.1.0967, 12/27/24, packaged 1/10)

current is 9.1.1074, so even sid is 107 patches behind. 9.0 went to patch 2190, so bookworm is 1886 patches behind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants