[opensuse-buildservice] topadd
Trying to change a _link file from <link project="home:RedDwarf" package="qmmp" > <patches> <topadd>%define _with_ffmpeg 1</topadd> <topadd>%define _with_mad 1</topadd> <topadd>%define _with_faad 1</topadd> </patches> </link> to <link project="home:RedDwarf" package="qmmp" > <patches> <topadd>%define _with_av 1</topadd> <topadd>%define _with_mad 1</topadd> <topadd>%define _with_faad 1</topadd> </patches> </link> returns validation failed, output: Relax-NG validity error : Extra element topadd in interleave /tmp/opensuse_frontend_validator20110402-25760-19u0251-0:4: element topadd: Relax-NG validity error : Element patches failed to validate content /tmp/opensuse_frontend_validator20110402-25760-19u0251-0 fails to validate Is topadd deprecated? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Samstag, 2. April 2011, 23:51:02 schrieb Cristian Morales Vega: ..
validation failed, output: Relax-NG validity error : Extra element topadd in interleave /tmp/opensuse_frontend_validator20110402-25760-19u0251-0:4: element topadd: Relax-NG validity error : Element patches failed to validate content /tmp/opensuse_frontend_validator20110402-25760-19u0251-0 fails to validate
Is topadd deprecated?
No, but api is validating the xml. It did not accept multiple topadd elements so far. I have changed this in git. A workaround for now is to use just one topadd element. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2011-04-04 14:02:37 +0200, Adrian Schröter wrote:
Am Samstag, 2. April 2011, 23:51:02 schrieb Cristian Morales Vega: ..
validation failed, output: Relax-NG validity error : Extra element topadd in interleave /tmp/opensuse_frontend_validator20110402-25760-19u0251-0:4: element topadd: Relax-NG validity error : Element patches failed to validate content /tmp/opensuse_frontend_validator20110402-25760-19u0251-0 fails to validate
Is topadd deprecated?
No, but api is validating the xml. It did not accept multiple topadd elements so far. I have changed this in git.
A workaround for now is to use just one topadd element.
this was the planned way and given that you can use newlines inside a topadd element, having multiple topadd doesnt make any sense. can we revert that change please? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Apr 05, 2011 at 12:17:26PM +0200, Marcus Rueckert wrote:
this was the planned way and given that you can use newlines inside a topadd element, having multiple topadd doesnt make any sense. can we revert that change please?
No, multiple topadds make perfect sense (and they were supported right from the beginning). You can also intermix them with other patch elements. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2011-04-05 13:48:40 +0200, Michael Schroeder wrote:
On Tue, Apr 05, 2011 at 12:17:26PM +0200, Marcus Rueckert wrote:
this was the planned way and given that you can use newlines inside a topadd element, having multiple topadd doesnt make any sense. can we revert that change please?
No, multiple topadds make perfect sense (and they were supported right from the beginning). You can also intermix them with other patch elements.
what different semantics do i get from <topadd>%define foo 1</topadd> <topadd>%define bar 1</topadd> versus? <topadd> %define foo 1 %define bar 1 </topadd> darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 5. April 2011, 13:57:58 schrieb Marcus Rueckert:
On 2011-04-05 13:48:40 +0200, Michael Schroeder wrote:
On Tue, Apr 05, 2011 at 12:17:26PM +0200, Marcus Rueckert wrote:
this was the planned way and given that you can use newlines inside a topadd element, having multiple topadd doesnt make any sense. can we revert that change please?
No, multiple topadds make perfect sense (and they were supported right from the beginning). You can also intermix them with other patch elements.
what different semantics do i get from <topadd>%define foo 1</topadd> <topadd>%define bar 1</topadd>
versus?
<topadd> %define foo 1 %define bar 1 </topadd>
none -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Apr 05, 2011 at 02:02:09PM +0200, Adrian Schröter wrote:
Am Dienstag, 5. April 2011, 13:57:58 schrieb Marcus Rueckert:
On 2011-04-05 13:48:40 +0200, Michael Schroeder wrote:
On Tue, Apr 05, 2011 at 12:17:26PM +0200, Marcus Rueckert wrote:
this was the planned way and given that you can use newlines inside a topadd element, having multiple topadd doesnt make any sense. can we revert that change please?
No, multiple topadds make perfect sense (and they were supported right from the beginning). You can also intermix them with other patch elements.
what different semantics do i get from <topadd>%define foo 1</topadd> <topadd>%define bar 1</topadd>
versus?
<topadd> %define foo 1 %define bar 1 </topadd>
none
Actually <topadd>%define foo 1</topadd> <topadd>%define bar 1</topadd> is equivalent to <topadd> %define bar 1 %define foo 1 </topadd> Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Adrian Schröter -
Cristian Morales Vega -
Marcus Rueckert -
Michael Schroeder