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

Add Pijul resolver #554

Open
notramo opened this issue Apr 28, 2022 · 2 comments
Open

Add Pijul resolver #554

notramo opened this issue Apr 28, 2022 · 2 comments

Comments

@notramo
Copy link

notramo commented Apr 28, 2022

Pijul is a distributed version control system. It's inspired by Darcs, but is written in Rust, and uses a different merge algorithm.
https://pijul.org/

@notramo
Copy link
Author

notramo commented Aug 19, 2022

@straight-shoota I am interested in implementing this. Would you accept a pull request?

@straight-shoota
Copy link
Member

I'm not very eager on this one. Introducing new resolver isn't a huge effort for the maintainers, if you're contributing the code. We'd still need to review and approve it. However, continuously maintaining the resolver is a more demanding task. I'm hesitant to do that for a niche feature.

Honestly, I've never heard about Pijul before. We've recently added some alternative SCM resolvers besides git, but they seem to be a lot more popular than Pijul. And even that was a big leap, considering how much baggage we might now be dragging along. I would rather wait a bit to see how things go with the latest additions, before incorporating new, even lesser used resolvers.

For the meantime, maybe you could fork shards and add a Pijul resolver in your fork. This would allow people to use it, without immediately adding a maintenance burden on the upstream project.
And please direct interested parties to this issue to give it a thumbs up, so we can gauge demand for this resolver.

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

No branches or pull requests

2 participants