Vladimir Panteleev

Unfortunately this is not easily possible, due to how file enumeration is currently done.

It would mean reimplementing [this block](https://github.com/CyberShadow/aconfmgr/blob/c95a65b00536ab80f81359d113a1c9ab7431136d/src/common.bash#L142-L194), however it could mean a massive performance decrease and a large increase in code complexity.

I guess it would be possible by making each `AddPath` instance correspond to a `find` invocation (i.e. there being an implicit `AddPath /`), then ignore `IgnorePath` rules which match the...

> It would pass the --noconfirm flag to pacman instead of piping `yes` command to it We can't do that for package installation because pacman defaults some prompts to "no"....

Right. That said, if both situations can be resolved by changing the aconfmgr configuration to one such that pacman does not produce either type of prompt, then not piping `yes`...

There's two relevant situations that can occur here. The first one is the one that cd1c4b0f46c23ddf763f37f9d6c930f272690d9f attempted to address: - **Conditions**: aconfmgr requests pacman to install a package which conflicts...

See https://github.com/CyberShadow/aconfmgr/issues/23#issuecomment-356178109 for some discussion on aconfmgr automatically updating package repositories. I think prompting the user whether they'd like to sync repositories if the pacman configuration was updated (ideally, specifically,...

New features can be added to aconfmgr as soon as either someone contributes a pull request or when I'm able to allocate a time window to work on aconfmgr enhancements...

Could you please run `aconfmgr` with the `-x` shell flag (e.g. `bash -x /usr/bin/aconfmgr`), and post the output? That should, at least, allow finding the failing command.

So, how can we act on this? Do you have a way to reproduce the problem?