[opensuse-buildservice] Parser chokes on %if 0%{?suse_update_desktop_files:1}
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The parser doesn't seem to be able to catch
%if 0%{?suse_update_desktop_files:1}
Not that it's necessarily needed to be able to handle all the possible
spec file notations with stuff like that but... is the limitation wrt
knowing whether that macro is defined in /usr/lib/rpm/*, or with the
notation 0%{xxx:1} ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Sun, Apr 29, 2007 at 01:28:43AM +0200, Pascal Bleser wrote:
The parser doesn't seem to be able to catch %if 0%{?suse_update_desktop_files:1}
Not that it's necessarily needed to be able to handle all the possible spec file notations with stuff like that but... is the limitation wrt knowing whether that macro is defined in /usr/lib/rpm/*, or with the notation 0%{xxx:1} ?
The former, %suse_update_desktop_files is not defined in the distribution config. I never thought someone would put a BuildRequires line into such an %if statement, what exactly do you want to achieve? 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Schroeder wrote:
On Sun, Apr 29, 2007 at 01:28:43AM +0200, Pascal Bleser wrote:
The parser doesn't seem to be able to catch %if 0%{?suse_update_desktop_files:1}
Not that it's necessarily needed to be able to handle all the possible spec file notations with stuff like that but... is the limitation wrt knowing whether that macro is defined in /usr/lib/rpm/*, or with the notation 0%{xxx:1} ?
The former, %suse_update_desktop_files is not defined in the distribution config.
It is a macro from /usr/lib/rpm/suse_macros though ;)
I never thought someone would put a BuildRequires line into such an %if statement, what exactly do you want to achieve?
Well, if that macro is available (which means on SUSE >= 9.x, which is
why I just replaced it with a check on %suse_version), I use it.
If not, I don't.
It's not critical, as I was able to replace it with a check on the suse
version, but just curious what the spec parser supports and what not.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Tue, May 01, 2007 at 10:35:05AM +0200, Pascal Bleser wrote:
Well, if that macro is available (which means on SUSE >= 9.x, which is why I just replaced it with a check on %suse_version), I use it. If not, I don't.
It's not critical, as I was able to replace it with a check on the suse version, but just curious what the spec parser supports and what not.
The spec parser would support it, but the macro is just not defined in the project configuration. 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 (2)
-
Michael Schroeder -
Pascal Bleser