On 21 July 2015 at 14:58, Tim Groeneveld <tim@timg.ws> wrote:
That .conf file would be downloaded, and then placed into /etc/pacman.d
Why not point to a package similar to 'pacman-mirrorlist' for that mirror, this way the file in /etc/pacman.d/ can be managed in the future by updates to that package in the repo it's adding? eg, # repo-add repo.example.com 1. Search for TXT record of repo.example.com == http://repo.example.com/any/example-mirrorlist.pkg.tar.gz 2. pacman -U the TXT RR 3. The mirrorlist file is now manage in an ongoing basis (assuming the package actually exists in the 3rd party repo) This is of course a roundabout way of just running `pacman -U http://repo.example.com/any/example-mirrorlist.pkg.tar.gz` which is the more KISS way IMHO, although I see how having the 'repo-add' command would look/feel more polished.