[opensuse-buildservice] Source RPMs in OBS

When I build packages in OBS, I get a source RPM for each architecture (e.g., i586, x86_64). I am curious what the differences might be in these source RPMs. I would guess there are two possible sources of differences: the package's .spec file and the OBS macros used when making the source RPMs. Are there directives in either of these that are resolved when the source RPM is built, resulting in a different source RPMs on a specific platform? I ask because I am considering making a local copy of the source RPMs I have in OBS so that, in an emergency, they can be used to rpmbuild --rebuild the package locally. This is working fantastic for me. But I have been using the source rpm for each platform. Do I really need to do this? The built binary RPMs I build locally are, of course, for the platform on which I run rpmbuild. Does this question make sense? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wednesday 2016-10-05 09:33, Roger Oberholtzer wrote:
When I build packages in OBS, I get a source RPM for each architecture (e.g., i586, x86_64). I am curious what the differences might be in these source RPMs. I would guess there are two possible sources of differences: the package's .spec file and the OBS macros used when making the source RPMs. Are there directives in either of these that are resolved when the source RPM is built, resulting in a different source RPMs on a specific platform?
Yes, you can do fancy things with prjconf. %ifarch x86_64 Substitute: foobar-devel foo64-devel %else Substitute: foobar-devel foo32-devel %endif and since that is a change done before rpmbuild is called, both .src.rpms will be different. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wed, Oct 5, 2016 at 2:55 PM, Jan Engelhardt <jengelh@inai.de> wrote:
Yes, you can do fancy things with prjconf.
%ifarch x86_64 Substitute: foobar-devel foo64-devel %else Substitute: foobar-devel foo32-devel %endif
and since that is a change done before rpmbuild is called, both .src.rpms will be different.
Moral of the story: I need to get all the various source RPMS. Just so I know. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wednesday 2016-10-05 15:30, Roger Oberholtzer wrote:
On Wed, Oct 5, 2016 at 2:55 PM, Jan Engelhardt <jengelh@inai.de> wrote:
Yes, you can do fancy things with prjconf.
%ifarch x86_64 Substitute: foobar-devel foo64-devel %else Substitute: foobar-devel foo32-devel %endif
and since that is a change done before rpmbuild is called, both .src.rpms will be different.
Moral of the story: I need to get all the various source RPMS. Just so I know.
Well the moral of it is: publish the prjconf, and publish the source files (possibly via an OBS itself, or a tar archive). I can't remember the last time I needed something in *srpm* format from openSUSE. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wed, Oct 5, 2016 at 4:11 PM, Jan Engelhardt <jengelh@inai.de> wrote:
Well the moral of it is: publish the prjconf, and publish the source files (possibly via an OBS itself, or a tar archive). I can't remember the last time I needed something in *srpm* format from openSUSE.
I find them very useful. Especially if I need to build an RPM for an older openSUSE that is no longer built in OBS. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Jan Engelhardt
-
Roger Oberholtzer