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

[FeatureRequest] Separate out the pmm frontend into a package of its own. #261

Open
Animeshz opened this issue Apr 12, 2022 · 5 comments
Open

Comments

@Animeshz
Copy link

Animeshz commented Apr 12, 2022

The pmm frontend concept is quite useful not just in bedrock but also in the outside world too.

Sometimes we are familiar with certain package manager frontend, but sometimes we force-fully have to use some other distro/package-manager due to certain reasons, and we loose alot of time just by searching how another package manager work because the frontend supported by the distro is not in our taste.

Hence if the frontend used in pmm to mimic package manager of different distro be separated out into a minimal package of its own, it'll be quite useful!

Thanks for the consideration 😄

@Animeshz
Copy link
Author

It'll also be more easy for the development of pmm frontend as a discrete project, as more and more people be able to add options and its mapping to different package manager they know of, because of the smaller codebase it will depends to.

@aadi58002
Copy link

The concept of having a common front end to all package manages makes it simpler to switch between distro and not worry about the specific command of the distro has to do general package managerment.

@paradigm
Copy link
Member

paradigm commented Apr 12, 2022

In addition to the front-end flexibility pmm offers, traditional distros also support multiple package managers, e.g. pip, cargo, etc. I think the full suite of pmm functionality would be useful on traditional distros, even if it's less so than on Bedrock.

The Bedrock Linux 0.8 roadmap includes a complete rewrite of pmm. This will include a number of fairly substantial improvements, including performance improvements, the ability to run package manager operations in parallel, per-user (rather than system wide) configuration, a scriptable interface, etc. I'll definitely consider writing it to work on traditional distros at this time. However, it'll may be a bit; I want to get the core 0.8 features into a publically testable alpha state before support utilities like pmm get any development resources.

@Animeshz
Copy link
Author

Ping me up if any help is needed!

I've been using and tinkering bedrock for about a month on my raspberry pi, nothing broken, great experience so far, got a fair bit of idea of this environment. I'm curious to know how complete rewrite of pmm would be 👀

@paradigm
Copy link
Member

If I remember I will reach out, but I'm likely to forget. I'm well equipped to manage the technical aspects of Bedrock, but I'm so greatly outnumbered by the community that I have difficulty tracking individuals. I'll almost certainly make public announcements about 0.8, e.g. when it's ready for public testing. If you keep an eye out for news either on the website or github you'll likely catch when things are ready for testing and be able to provide useful feedback then.

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

3 participants