giving options to use a custom pacman.conf

[moodyhunter]

firstly, thanks for the great project :)

when building packages for the testing repo, e.g. tracking packages versions from the testing repository:

# following testing/gdb version
update_on:
  - source: alpm
    alpm: gdb
    repo: testing

However, this seems impossible without adding [testing] entries into my own /etc/pacman.conf

(Of course one doesn't want to do so, even appending testing at the end of the file makes me feel it nasty)

I'd suggest adding an option for providing one's custom pacman.conf.

PS: I know packages in testing will be removed as soon as they are stabilized, but this issue does apply to other cases: "package for repo X when one doesn't want X to be configured on the build machine"

[lilydjwg]

This needs to be added in nvchecker. Would you like to create a pull request for this?

[moodyhunter]

I'm familiar with neither lilac nor nvchecker, but I'll dive deeper and (hopefully) PR for this.

[moodyhunter]

It seems that nvchecker is using a custom dbpath pre-allocated by lilac, IMO it's lilac's responsibility to set up the pacman db (that is to be checked by nvchecker) from the given pacman.conf

[Hayao0819]

I too would like it to use lilac on manjaro for building archlinux packages. If lilac could support the option to run build other than extra-x86_64-build command, you can only build with your custom pacman.conf but cannot auto package update and others.

[Hayao0819]

This issue may also be related to #155

[lilydjwg]

If lilac could support the option to run build other than extra-x86_64-build command

You can specify any devtools command (including your own) in lilac.yaml (the schema specifies a few choices but lilac doesn't check that).

[Hayao0819]

I hope the option to set default command in ~/.lilac/config.toml