rpm-rs
rpm-rs copied to clipboard
Status of this project
Hello @Richterrettich, may I know if this project is actively worked on? We have planned to create an alternative package manager for openSUSE called rypper. It is a learning project for me and my friends and I suggested we use this crate. If this is not actively worked on, we can just fork this and improve a lot of stuff that might got overlooked.
I will wait for your response!
Would love to maintain rpm-rs with you @uncomfyhalomacro. ❤️
Commenting to stay in the loop - I want to use this crate in https://github.com/cmeister2/remote-package but it uses an outdated zstd, which is causing some issues.
EDIT: I forked this and renamed it fez
; mostly just to get up to date dependencies.
@cmeister2 Thank you!
@cmeister2 Thank you!
Shiny, just so you know, i think we will have to fork this project and update some stuff. I was not able to stay in the loop so I will have to read some things here and there
@Richterrettich Is there a chance you could add a new maintainer such as @drahnr or myself if you do not have time to actively maintain the crate?
I'm maintaining https://github.com/dralley/rpmrepo_metadata and eventually this crate is likely to be one of my critical dependencies.
Hey 👋, I forked rpm-rs in the past due to inactivity here. I tend to prefer creating entities around projects so they're not bound to individuals that much anymore. That could also be an option for rpm-rs
From my perspective I don't really mind where we go from here. I forked this to https://github.com/cmeister2/fez , updated the dependencies as far as I could in limited time and added the feature I wanted (ability to read the metadata without reading in the whole package).
I'd love the community to coalesce around a single place, wherever that might be. I have a list of improvements that I'd love to make to fez to make it really useful, but equally I'm happy to make patches too.
On Thu, 23 Jun 2022, 06:37 Bernhard Schuster, @.***> wrote:
Hey 👋, I forked rpm-rs in the past due to inactivity here. I tend to prefer creating entities around projects so they're not bound to individuals that much anymore. That could also be an option.
— Reply to this email directly, view it on GitHub https://github.com/Richterrettich/rpm-rs/issues/54#issuecomment-1163969157, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPA36KXNNYPFWZKTO4BEDDVQPZ3JANCNFSM5WEKVE6Q . You are receiving this because you were mentioned.Message ID: @.***>
@cmeister2 I will be interested to contribute and use yours 😄 but it take a while. I have lots of stuff to do at uni so most of my time doing projects are postponed for now
Hi! I'd love to also maintain this project. We would like to use this for our own alternative package manager for Fedora called anda. It would be very useful to have a pure-rust implementation of RPM.
I took the liberty to create https://github.com/rpm-rs and invited all interested parties to keep the ball rolling, any 2 approvals of the people invited can merge changes. Any of this is up to discussion obviously, but let's keep talking there :)
Neat, I didn't know that was a supported feature of github, thank you :)
I assume that @Richterrettich is still needed to perform publishes however, at least without changing the crate name?
Speaking of, I emailed him a few days ago, waiting on a response.
Neat, I didn't know that was a supported feature of github, thank you :)
I assume that @Richterrettich is still needed to perform publishes however, at least without changing the crate name?
Speaking of, I emailed him a few days ago, waiting on a response.
Cool! I wonder if he is still active. It seems his GitHub activity is inactive...
although if we want to create a new name, i thought of a funny one
rawr - RPM Another Rewrite in Rust 😄
Happy to give people collaborative permissions on fez
- pretty sure I'm
up to date on all the dependabot issues now. Obviously would be cleaner if
there was a separate official fork to rpm-rs though.
On Tue, 19 Jul 2022, 16:45 Soc Virnyl S. Estela, @.***> wrote:
although if we want to create a new name, i thought of a funny one
rawr - RPM Another Rew**rite in Rust 😄
— Reply to this email directly, view it on GitHub https://github.com/Richterrettich/rpm-rs/issues/54#issuecomment-1189217995, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPA36OVWIFGUWFIMPF7GVLVU3ESLANCNFSM5WEKVE6Q . You are receiving this because you were mentioned.Message ID: @.***>
That's what I tried with an org that's independent, another user owned repo doesn't solve the underlying issue really.
@cmeister2 you could probably join the org or should we focus on your fork?
Happy to join the org, don't appear to have any invites in my email though. Doesn't solve the package name issue though.
On Tue, 19 Jul 2022, 16:56 Soc Virnyl S. Estela, @.***> wrote:
@cmeister2 https://github.com/cmeister2 you could probably join the org or should we focus on your fork?
— Reply to this email directly, view it on GitHub https://github.com/Richterrettich/rpm-rs/issues/54#issuecomment-1189230249, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPA36JJDCZEEORTHIZMDNTVU3F2RANCNFSM5WEKVE6Q . You are receiving this because you were mentioned.Message ID: @.***>
Just a heads up. Still "new" to rust because I haven't coded for a while and I never made any major projects yet so I decided to create one called rypper, a rewrite of a package manager for opensuse. The only problem is this library which seems to be an experiment of some sort, hence, the inactivity. And since this is open source, I guess I won't be too worried about your forks.
@cmeister2 you could probably join the org or should we focus on your fork?
We could also ask for permission to move to the official RPM organization, but it already has a FFI binding crate for RPM there.
@cmeister2 you could probably join the org or should we focus on your fork?
We could also ask for permission to move to the official RPM organization, but it already has a FFI binding crate for RPM there.
I oppose that. The development was never meant to become a fully featured rpm implementation with all the cruft. And I fear that precisely this cruft would like into the implementation. At the other hand, I don't see an upside to migrating to the rpm org.
Github does not seem to send invites properly when creating the org, so I invited you again.
@cmeister2 you could probably join the org or should we focus on your fork?
We could also ask for permission to move to the official RPM organization, but it already has a FFI binding crate for RPM there.
I oppose that. The development was never meant to become a fully featured rpm implementation with all the cruft. And I fear that precisely this cruft would like into the implementation. At the other hand, I don't see an upside to migrating to the rpm org.
Github does not seem to send invites properly when creating the org, so I invited you again.
Thanks for that. I've created an MR for most of the changes I made - I haven't included:
- my
RpmPkgReader
change. (I do want this in, it shouldn't be part of the MR) - the relicense to MIT (I prefer MIT, but I guess I can work within the bounds of Apache-2.0)
We could also ask for permission to move to the official RPM organization, but it already has a FFI binding crate for RPM there.
I oppose that. The development was never meant to become a fully featured rpm implementation with all the cruft. And I fear that precisely this cruft would like into the implementation. At the other hand, I don't see an upside to migrating to the rpm org.
@drahnr @korewaChino For what it's worth, I know many of those people and have a video call with them once a month, I'm able to reach out if that was something we did want to do. I wouldn't ask unless @Richterrettich was on board, however, that would feel improper. (I'm assuming he will come back eventually).
I don't think there's any expectation that just because it's in the official organization that it's a complete implementation. I've asked before with one of my libraries and while I didn't end up bothering to go through with it (yet) they were fine with the idea, even if it wasn't "complete", so long as it didn't get ditched and start bitrotting (which is unfortunately the state that librpm.rs is currently in).
But yes, I don't know that it is necessary or useful, so long as the bus factor is > 1.
@drahnr I also need a new invite. Github has been extremely buggy lately, I've run into a bunch of issues in the past few weeks...
Done
@cmeister2 you could probably join the org or should we focus on your fork?
We could also ask for permission to move to the official RPM organization, but it already has a FFI binding crate for RPM there.
I oppose that. The development was never meant to become a fully featured rpm implementation with all the cruft. And I fear that precisely this cruft would like into the implementation. At the other hand, I don't see an upside to migrating to the rpm org. Github does not seem to send invites properly when creating the org, so I invited you again.
Thanks for that. I've created an MR for most of the changes I made - I haven't included:
* my `RpmPkgReader` change. (I do want this in, it shouldn't be part of the MR) * the relicense to MIT (I prefer MIT, but I guess I can work within the bounds of Apache-2.0)
Relicensing would (to my understanding) require a signoff by all contributors, which is non trivial to achieve, but the sooner the better. I have no strong opinion, I'd generally lean for a dual license iff we ought to change it.
It would, all existing contributors (including @Richterrettich) would need to agree to the license change, you cannot just slap a new license on it.
With that said, I have a few lines of code present and I consent, though my personal preference would be MPL v2 license.
@drahnr For some reason, I still don't have it. I checked spam, checked "promotions" tab, checked both personal and work emails. : /
edit: finally, it worked. Thanks!
@Richterrettich I don't know if you're busy (I do see some activity a few weeks ago) but it would be really great if you could weigh in - even if it's just to give your blessing to a forked package. There's currently no way to update crates.io without uploading a completely new package which would be best avoided if we can.
Anyone knows whether this project still maintained?
Well, https://github.com/rpm-rs is, if there are specific issues, feel free to file em there :)