FS#50174 - Inclusiong of option: --config <file>
Attached to Project:
Pacman
Opened by Hiroki Yamamoto (hirokiyamamoto) - Thursday, 28 July 2016, 09:23 GMT
Last edited by Allan McRae (Allan) - Thursday, 28 July 2016, 10:26 GMT
Opened by Hiroki Yamamoto (hirokiyamamoto) - Thursday, 28 July 2016, 09:23 GMT
Last edited by Allan McRae (Allan) - Thursday, 28 July 2016, 10:26 GMT
|
Details
Summary and Info:
Allow pacman to be invoked using an alternative configuration file. It's purpose is to allow completely seperate package databases / cache directories / log files / and other related configuration variables. Yes, this will expand the possibilities to do partial upgrades with seperate databases that don't have full insight in all packages installed on a system. Yes, this shifts the responsibility of proper repository maintenance to the user / administrator of the system. However, partial upgrades can already be done. Additionally, when using custom repositories, repository maintenance is already a very important part of using additional or exclusively custom repositories. Steps to Reproduce: None. |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 28 July 2016, 10:26 GMT
Reason for closing: Not a bug
Additional comments about closing: man pacman
Thursday, 28 July 2016, 10:26 GMT
Reason for closing: Not a bug
Additional comments about closing: man pacman