Live data from Hacker News

GitHub: sysget – A front-end for every package manager

github.com

1–10 of 64 posts

Re: GitHub: sysget – A front-end for every package manager

#3
post #2

How does this handle edge cases like needing to run 'brew link' etc. occasionally? What happens when multiple package managers provide the same package?

A look at the source code shows that it decides what package manager it should use by using a config file, and to install a package it runs system("brew install asdf") so I guess you would see a message telling you to run 'brew link' from the homebrew output.

Re: GitHub: sysget – A front-end for every package manager

#8
post #4

Seems like a cool idea! Just a thought, what if you allowed it to run in different modes, for people used to different systems? apt mode, yum mode, pacman mode etc to accept commands in that format.

I think this would make it needlessly complex. The idea is to have it be the same everywhere.

I’d be happy to learn a new syntax if that was the last time I had to deal with it.

Re: GitHub: sysget – A front-end for every package manager

#10
I like this. This makes a lot of sense to me. If it managed to gain adoption into major distros, it would be incredibly good, though obviously that is a longshot for a lot of reasons.

If you really want it to get adopted into major distros, the best approach is probably to convince the systemd folks that it would be a great addition to their package ;)

edit: A bit of constructive criticism. I really like the concept, but I think the way that package managers are supported could be improved. I think it would be better if all of the handlers for a given package manager were in the same file, instead of having them spread across every file. There's obviously lots of ways to accomplish this.

Also, as it is now, this project does not seem to use a ton of things that require C++ - you could shave some binary size cost by converting it to pure C.

Post reply on HN