Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#34551 - pacman: add functionality of user-defined meta packages
Attached to Project:
Pacman
Opened by mark (mmm) - Monday, 01 April 2013, 15:41 GMT
Last edited by Dave Reisner (falconindy) - Friday, 14 June 2013, 20:00 GMT
Opened by mark (mmm) - Monday, 01 April 2013, 15:41 GMT
Last edited by Dave Reisner (falconindy) - Friday, 14 June 2013, 20:00 GMT
|
DetailsHi, I'd like to propose a feature to pacman/makepkg, allow users to create new meta-packages quickly.
Just let them define name,[description],and dependencies. I imagine something like: $pacman --meta myNvidia --desc "local NV install with openCL" --depends nvidia, opencl, someother<=1.3.37 which would create a PKGBUILD with appropriate (name,desc,depends, provides,conflicts) fields, download deps, call makepkg, pacman -U the meta-package. Use-cases: #1 no more forgotten opt-depends disadvantage of today's optdepends is they are installed as explicit, so when i go through my list of packages to removed unused ones, I usually wonder what that lib/pkg is good for there. Meta pkg would handle this gratefully. #2 work projects I tend to work on several projects, where each requires specific apps for work, so I install them, when the project is over, I would like to wipe them off, but usually forget which were those. $pacman --meta midi --desc "computer generated music" --depends abcmidi,mp32midi,dino I think I could implement this in shell, but dont have enough pacman knowledge to do it in pacman itself. What do you think about the idea and design? I believe the implementation part shouldnt be too complex, as all tools are already in place, just to hook them up appropriately. Cheers, Mark |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 14 June 2013, 20:00 GMT
Reason for closing: None
Additional comments about closing: 3rd party tool meets the user's needs.
Friday, 14 June 2013, 20:00 GMT
Reason for closing: None
Additional comments about closing: 3rd party tool meets the user's needs.
https://bbs.archlinux.org/viewtopic.php?id=53788
and there's still his somewhat related tool makedep that you may want to look at:
http://xyne.archlinux.ca/projects/makedep/
Anyways, I mentioned Xyne here: https://bugs.archlinux.org/task/11337 (btw, nice bug# :), and asking for metapax sources + his opinion).
Mentioned to "yaourt people" here: https://aur.archlinux.org/packages/yaourt/ ,because I didnt find other place to reach upstream.
After I wrote the above, I took a look at the old code and started to rewrite a simplified version, but I quickly realized that the easiest way would be to simply create the .PKGMETA file manually and add it to an empty tar.xz archive.
Fwiw, I agree that this functionality is better left to a separate utility.
If you dont think pacman is a good place, I'll either make a separate script, or try to add it to yaourt/packer.
Should the bug be closed?
Cheers!
I think you should make a separate script. It is a package creator and should not be shoehorned into a package manager.
You can probably request closure of this thread as I doubt it will ever be implemented in Pacman.
https://github.com/andrewgregory/makepkg-meta
Would you like to make an AUR package? Or should I.
Many thanks, this is perfect.
The pkg is in AUR, everyone enjoy.
https://aur.archlinux.org/packages/makepkg-meta-git
I think we can close .. me going consolidate all the packages accumulated throught time.