Open lunics opened 1 year ago
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
cc @indrajitr @tchernomax click here for bot help
@lunics I'm curious why do you closed this as "not planned". Did you decide that this feature is not a good idea and should not be implemented in this module? Or is there another reason?
Hello @felixfontein, I thought it was pointless, ansible is maybe not made to integrate all parameters of everything. I keep the issue open in order to open up the debate.
It's basically up to community contributors to implement this. If somebody wants this feature enough to implement it by themselves, or if somebody wants to implement that for the fun of it (without needing it themselves), this will get implemented eventually. (I don't see a reason why the module shouldn't allow this.)
If I understand it correctly, pacman's --sysroot
parameter would be equivalent to using the chroot connection; --root
does something else.
Pacman itself doesn't have a way to specify a different root
pacman does have both a --sysroot
(for chroot) and a --root
(to specify an alternate installation root) parameter.
cc @jraby click here for bot help
Summary
I bypass the Arch Linux pacstrap's command with my own script, I would like to have an ansible pacman module with the -r/--root parameter to specify the path of my chroot. Regards
Issue Type
Feature Idea
Component Name
pacman
Additional Information
Code of Conduct