[opensuse-buildservice] Mono autogeneration of dependencies
Hi, Suse 10.1 and up have a patched rpm that autogenerates dependencies for mono assemblies. In my old build system, an .rpmrc file is used to specify additional macros for running extra scripts to generate this info. How would I go about doing this in the build service? Thanks, Wade --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
I can't say for certain, but I think I do something similar. A number of packages I build have a file that specifies additional macros, which sounds similar to what you're wanting to do. What I do is this: 1.) Include the contents of the .rpmrc as a source file (rpm_macros) 2.) Add to the rpm .SPEC file: Source9999: rpm_macros %include %{SOURCE9999} (it doesn't matter what the source # is; but 9999 can generally be pasted in to any RPM without causing a collision). On Thursday 05 April 2007, Wade Berrier wrote:
Hi,
Suse 10.1 and up have a patched rpm that autogenerates dependencies for mono assemblies.
In my old build system, an .rpmrc file is used to specify additional macros for running extra scripts to generate this info.
How would I go about doing this in the build service? -- Troy Telford
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, 2007-04-06 at 13:54 -0600, Troy Telford wrote:
I can't say for certain, but I think I do something similar. A number of packages I build have a file that specifies additional macros, which sounds similar to what you're wanting to do.
What I do is this: 1.) Include the contents of the .rpmrc as a source file (rpm_macros) 2.) Add to the rpm .SPEC file:
Source9999: rpm_macros %include %{SOURCE9999}
(it doesn't matter what the source # is; but 9999 can generally be pasted in to any RPM without causing a collision).
Very nice, thanks for the tip. Wade
On Thursday 05 April 2007, Wade Berrier wrote:
Hi,
Suse 10.1 and up have a patched rpm that autogenerates dependencies for mono assemblies.
In my old build system, an .rpmrc file is used to specify additional macros for running extra scripts to generate this info.
How would I go about doing this in the build service?
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-04-06 13:54:18 -0600, Troy Telford wrote:
(it doesn't matter what the source # is; but 9999 can generally be pasted in to any RPM without causing a collision).
and it will bloat your src.rpm as the rpm as the sources list is not sparse. so you will tons of empty entries in the array. 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 Fri, 2007-04-06 at 23:40 +0200, Marcus Rueckert wrote:
On 2007-04-06 13:54:18 -0600, Troy Telford wrote:
(it doesn't matter what the source # is; but 9999 can generally be pasted in to any RPM without causing a collision).
and it will bloat your src.rpm as the rpm as the sources list is not sparse. so you will tons of empty entries in the array.
maw@builder:~/builds/openSUSE:Factory/yelp> ls -1s *.src.rpm* 944 yelp-2.18.0-1.src.rpm-bloated 944 yelp-2.18.0-1.src.rpm-unbloated Both have 2 Sources. -bloated has a third, a dummy Source9999, as well. As we can see, having bloated .src.rpms is a SERIOUS problem! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Apr 06, 2007 at 11:40:06PM +0200, Marcus Rueckert wrote:
On 2007-04-06 13:54:18 -0600, Troy Telford wrote:
(it doesn't matter what the source # is; but 9999 can generally be pasted in to any RPM without causing a collision).
and it will bloat your src.rpm as the rpm as the sources list is not sparse. so you will tons of empty entries in the array.
Seems I was wrong about that. I assumed that there were empty entries because of the NOSOURCE and NOPATCH tags, but that's actually not true (and the NOSOURCE and NOPATCH content is pretty useless). Sorry for the confusion. 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 (5)
-
Marcus Rueckert -
Michael Schroeder -
Michael Wolf -
Troy Telford -
Wade Berrier