feat(cli): add pacman silent install source - #850
Conversation
|
PR author is not in the allowed authors list. |
|
@marmitar is attempting to deploy a commit to the Modem Team on Vercel. A member of the Team first needs to authorize it. |
|
Sorry, forgot to mention. I maintain the AUR package hunk and I plan on using it there. I'm using |
32aa94c to
1213173
Compare
|
@benvinegar could you please review this? Or implement an equivalent feature? |
|
Yep, taking a look, just wrapping my head around what it means to have 2 packages here: 
|
|
AUR packages are usually built from source, that's what the The un-updatable |
| * is replaced by rebuilding the checkout it came from, which is the developer's own workflow and | ||
| * not something a published version number should interrupt. | ||
| * | ||
| * AUR packages installed via pacman should be updated manually or via an AUR helper. |
There was a problem hiding this comment.
Minor wording nit: AUR packages aren’t installed by pacman directly. Could this say “Arch packages installed through pacman or an AUR helper” instead?
This comment was generated by Pi using GPT-5.6 Sol
| "hunkdiff": patch | ||
| --- | ||
|
|
||
| Support pacman/AUR installs via `HUNK_INSTALL_SOURCE=pacman`. |
There was a problem hiding this comment.
Could we clarify that this recognizes pacman/AUR-managed installs rather than adding an installation method? Maybe: “Recognize pacman/AUR-managed installations via HUNK_INSTALL_SOURCE=pacman and suppress automatic update notices for them.”
This comment was generated by Pi using GPT-5.6 Sol
No runtime detection for pacman, since different AUR packages may
install binaries at different locations (/opt, /usr/bin, /usr/lib).
Only viable detection is 'pacman -Qo ${executablePath}' or something
like 'rg ${executablePath} /var/lib/pacman/local/*/files'.
Both cases could affect startup time, so pacman is only available via
the 'HUNK_INSTALL_SOURCE' environment variable. Either bundled with
'--env "HUNK_INSTALL_SOURCE*"' or set at runtime from a custom wrapper.
Because of how pacman packages are managed, no update notices or
specific update instructions should be shown.
1213173 to
be6f045
Compare
No runtime detection for pacman, since different AUR packages may install binaries at different locations (/opt, /usr/bin, /usr/lib). Only viable detection is
pacman -Qo ${executablePath}or something likerg ${executablePath} /var/lib/pacman/local/*/files.Both cases could affect startup time, so pacman is only available via the
HUNK_INSTALL_SOURCEenvironment variable. Either bundled with--env "HUNK_INSTALL_SOURCE*"or set at runtime from a custom wrapper.Because of how pacman packages are managed, no update notices or specific update instructions should be shown.