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#14820 - new dependency-type field to link package <a> that requires rebuilding after package <b> is updated
Attached to Project:
Pacman
Opened by Brendan (watricky) - Monday, 25 May 2009, 02:40 GMT
Last edited by Allan McRae (Allan) - Sunday, 31 January 2016, 04:48 GMT
Opened by Brendan (watricky) - Monday, 25 May 2009, 02:40 GMT
Last edited by Allan McRae (Allan) - Sunday, 31 January 2016, 04:48 GMT
|
DetailsSummary and Info:
Certain custom packages, such as kernel modules, require rebuilding after updating another package, such as the kernel. Unfortunately at present there is no way to "link" the two in pacman's db. Steps to Reproduce: An example I've come across is virtualbox_bin in the archlinuxfr repository though I'm sure there are more. The post-installation notes for virtualbox_bin specifically say: > IMPORTANT NOTES: > > - Run "vbox_build_module" as root every time your kernel is upgraded, to > compile the module for the new kernel version. Proposed Solutions: Add either 1 or 2 new fields, similar to depends=() to aid in automating the above manual process. Unless you *remember* that you installed package A that requires commands to be executed when package B is updated, you might only notice issues after you've irreparably damaged important data (worst-case) or you've been battling to figure out why your application A isn't working (typical case). For now my thoughts are as follows: Solution A Run a command / series of commands automatically addtoinstall=(kernel26) addtoinstallcommand=vbox_build_module Solution B Print "special" notes automatically addnotes=(kernel26) notestext=/opt/virtualbox/rebuild-instructions.txt Solution C *Advise* reinstallation of package reinstalldepends=(kernel26) After kernel update, ask: archlinuxft/virtualbox_bin advises reinstallation after update of kernel26. Proceed? [Y/n] Personally, I'm in favour of C as it is the simplest and probably the most reliable. It *may* not fit all cases. B is the least "dangerous" and would at least give an appropriate warning when doing updates. It is not foolproof however. A is probably the most direct solution. |
This task depends upon
Closed by Allan McRae (Allan)
Sunday, 31 January 2016, 04:48 GMT
Reason for closing: Implemented
Additional comments about closing: Can be handled by Hooks
Sunday, 31 January 2016, 04:48 GMT
Reason for closing: Implemented
Additional comments about closing: Can be handled by Hooks
:D
I don't see hooks in bugzilla. Is this still in the vaporware stage?