On 01/31/2011 11:09 AM, Ludwig Nussel wrote:
Dave Plater wrote:
On 01/31/2011 09:29 AM, Vincent Untz wrote:
Le lundi 31 janvier 2011, à 02:44 +0200, Dave Plater a écrit :
Putting %dump in the spec file doesn't show up anything.
It's to make it possible to build the gstreamer packages in packman (or any other places) with the codecs that we can't build in the build service, while still sharing the same source packages.
It's basically like a bcond but I still don't understand where it's definition lives.
Nowhere :-) You can define %BUILD_ORIG and %BUILD_ORIG_ADDON in your ~/.rpmmacros, pass the definition to the build script via --define or put it in the project config. xine uses bconds¹ instead. It would be nice if the method could finally be unified.
bcond lives in /usr/lib/rpm/macros, when I came across it in xine-lib I found averything I needed to understand it there. BUILD_ORIG otoh isn't in my 11.3 systems /etc/rpm or /usr/lib/rpm and wasn't even part of a %dunp in an osc build openSUSE_Factory, I haven't tried an online one but if the macro works it must be hard coded into rpm or something. I've seen it for the first time in gstreamer plugins bad just after I'd tried to get the update service running unsuccessfully and thought I'd broken the 11.3 build somehow due to an error that appears at the beginning of the rpmbuild part of the build.
Is there some sort of liaison with packman and videolan, it's quite an important thing for multimedia?
AFAIK only for xine-lib. It would be desirable to combine efforts on gstreamer and other dupliated spec files as well though.
At least the gstreamer spec files are easier to work with, have a look at the xine-lib one, it's overloaded with bconds and %if suse_versions and very confusing.
Well, xine has lots of features, can be compiled for older distros still and the spec file is identical on Factory and packman ...
I haven;t been around packaging long enough to have picked that up, I could most probably browse the openSUSE site for days and not find it, thanks for the link. I've decided to leave xine-lib alone, I have a funny feeling that I could cause trouble by submitting an update to factory besides it seems to work remarkably well :-X Thanks Dave P