[opensuse-buildservice] osc: question about oscrc config
Hi All, In oscrc, current osc will record all the configuration directives in [general] section, but for each apiurl's specific section(s), only supported directives will be recorded. If osc select to record all ones in apiurl sections, it will be easier to expand the functions via plugins. So I want to know whether it's designed on purpose? Otherwise why not change it. My local patches are already tested, actually it's really simple:) Thanks, JF Ding -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2010-01-15 16:20:11 +0800, JF Ding wrote:
In oscrc, current osc will record all the configuration directives in [general] section, but for each apiurl's specific section(s), only supported directives will be recorded. If osc select to record all ones in apiurl sections, it will be easier to expand the functions via plugins. So I want to know whether it's designed on purpose? I don't know if it was designed like this but the current concept makes sense. Imagine you want to change the default value of an option and you would have to do this in _all_ "[apiurl]" sections... What we could easily support is the following: we still use the "[general]" section but we can override "[general]" settings in an "[apiurl]" section.
Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
I was thinking of implementing per repository config options too. The rpm in Ubuntu 9.10 does not read the signing portion of SLES 10 generated rpms correctly, so I always have to build SLE_10 rpms with --no-verify (on Ubuntu 9.10). I was just going to add a [SLE_10] no-verify = 1 to the ~/.oscrc so I could call osc indirectly through my svndownstream command. On Fri, 2010-01-15 at 07:28 -0600, Marcus Hüwe wrote:
On 2010-01-15 16:20:11 +0800, JF Ding wrote:
In oscrc, current osc will record all the configuration directives in [general] section, but for each apiurl's specific section(s), only supported directives will be recorded. If osc select to record all ones in apiurl sections, it will be easier to expand the functions via plugins. So I want to know whether it's designed on purpose? I don't know if it was designed like this but the current concept makes sense. Imagine you want to change the default value of an option and you would have to do this in _all_ "[apiurl]" sections... What we could easily support is the following: we still use the "[general]" section but we can override "[general]" settings in an "[apiurl]" section.
Marcus
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
JF Ding -
Luke Imhoff -
Marcus Hüwe