Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18198 - [ardour] build with syslibs cancels upstream support

Attached to Project: Arch Linux
Opened by Philipp (hollunder) - Saturday, 06 February 2010, 17:30 GMT
Last edited by Giovanni Scafora (giovanni) - Sunday, 07 February 2010, 20:20 GMT
Task Type General Gripe
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
From scons --help output:

SYSLIBS: USE AT YOUR OWN RISK: CANCELS ALL SUPPORT FROM ARDOUR AUTHORS: Use existing system versions of various libraries instead of internal ones (yes|no)
default: 0

The package in [extra] is for some reason built with SYSLIBS=1 despite this very explicit recommendation.

I know from watching #ardour every day that this isn't an empty warning and I'm quite sure that the author has good reason for this.


Additional info:
* package version(s)
Ardour 2.8.6

* config and/or log files etc.

This task depends upon

Closed by  Giovanni Scafora (giovanni)
Sunday, 07 February 2010, 20:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in ardour-2.8.7-1
Comment by Philipp (hollunder) - Saturday, 06 February 2010, 18:09 GMT
I talked with the main author about this and I'm partly quoting directly from IRC. I hope this helps to understand the reasoning behind it.

Arguments against SYSLIBS=1:
(a) "this caused breakage of the whole app on ubuntu, because of an "upgrade" to a library"
(b) "the ardour project will not support our users"

(b) will not be true if its possible to satisfy two conditions ...
las: my stance on syslibs is softening :) as long as the packager can guarantee two things, then we're good
las: they are (1) ardour must be built with the same precise compiler as was used for the libraries, and with no "odd" compiler flags
las: (2) ardour is set to depend on g++ as well as the libraries in a way that will invalidate an independent upgrade of either

Loading...