Bug 671206

Summary:	explicit disable ruby/csharp (and others?)
Product:	[Fedora] Fedora	Reporter:	Oliver Falk <oliver>
Component:	libcaca	Assignee:	Matthias Saou <matthias>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	matthias
Target Milestone:	---	Keywords:	EasyFix
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	0.99-0.12.beta17.fc16	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-11 14:07:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Oliver Falk 2011-01-20 18:35:22 UTC

You should really add --disable-ruby and --disable-csharp to your configure options. If you need to rebuild the package for some reason on a server where one of the above mentioned languages is installed, it tries to build the bindings...

That's true for all branches. Not only rawhide.

Comment 1 Matthias Saou 2011-07-11 12:16:06 UTC

What exact version/release of the package were you using? I'm asking because the ruby bindings have been enabled for a while already :

* Wed Apr 28 2010 Matthias Saou <http://freshrpms.net/> 0.99-0.10.beta17
- Update to 0.99.0beta17.
- Update spec file URLs.
- Switch to using DESTDIR for install, which is the preferred method.
- Remove the static library (#556062).
- Remove no longer needed libGLU patch.
- Enable new ruby bindings.
- Leave C# and Java disabled, I hope no one will ever ask to have them enabled.

I'm OK with explicitly disabling the ones I left disabled (C# and Java), but I won't be pushing updated packages just for this as it doesn't make sense, so be sure to use the latest available spec file from git if you want to rebuild.

Comment 2 Oliver Falk 2011-07-11 12:39:27 UTC

Actually this is quite some time ago... I can't remember which spec I was using. However, I would recommend to add explicit --enable-<language> and --disable-<language> to the specfile just to be sure nothing get's build by accident or get's not built by accident.
And yes, don't push out an update just because of this, but with the next update...