Fix libalpm not found #90

[imfulee]

Trying to fix #90
Bump version of alpm to v4.0.1. It seems to build fine on my arch machine, not sure what would happen on Debian based distros

[moberer]

Is there anything stopping this from being merged?

[ironashram]

Is there anything stopping this from being merged?

i guess the maintainer being busy/absent is the only thing stopping it

[ripytide]

@InnocentZero and I have been working on a fork of this project (https://github.com/ripytide/pacdef) for a few months and experimenting with several ideas for improvements and new features. Now I believe the code is in a more stable state I thought I'd mention it here in case those interested might like to try it out and give any feedback.

Some of the important changes:

• Removed cargo features and switched to purely command based backend package manager interaction so this particular bug cannot ever happen again to any of the supported backends. (It also make installing pacdef easier as all backends are supported out of the box without having to enable any extra cargo features)
• Switched group files to toml format to allow per-package per-backend installation options (also you get syntax highlighting and other ide-provided benefits for free)
• New pacdef add command to add new packages to you group files from the command line (just like the cargo add command for rust dependencies)
• removed non-core pacdef commands (import, export, list, new, remove, show, search) since they are all possible via more traditional linux programs like ln/cat/touch/rm/grep etc.. and so go against the unix philosophy.
• temporarily removed the review command while further discussing improvements Do we really need a ratatui frontend? ripytide/metapac#14 Review Resume #62 'pacdef package review' enhancement suggestions #36

[moberer]

I really appreciate the work @ripytide, though I think you should maybe consider giving your fork a different name to avoid confusion; (Even just something like pacdef-ng); And perhaps add a note in the Readme; -- Especially if you intend on publishing your version on AUR too.

[ripytide]

@moberer The intention was always to make a pull request upstream to avoid splitting the maintenance effort so on. The changes to the public facing configs as well as the code are very large in that most of it has been rewritten. Due to the scale of changes it would probably have to be released as pacdef v2.0.0 if it were merged upstream ripytide/metapac#23 . This of course all depends on @steven-omaha's opinion of the changes and whether or not he agrees with them for his project. If he didn't agree then I would happily rename and fork to let both projects exist. If @steven-omaha would agree to the changes then I might ask if we can move to a GitHub Org based repo to allow all of the prominent contributors full permissions.

Another possibility is that @steven-omaha is too busy at the moment to devote any time to this project (which is totally understandable) so I may also temporarily rename and publish to the AUR until if or when they have the time to discuss things.

[thdxr]

not sure if this PR fixes it - arch disappears as a supported backend?

[ripytide]

@thdxr That's due to pacdef using cargo features for the arch and apt backends so they are not enabled by default, another thing I've fixed in the fork.

[ripytide]

I've now renamed my fork of pacdef to metapac and published it to the AUR as metapac and metapac-bin as I think it is ready for usage though it probably contains quite a few bugs due to the amount of code changes that have happened.