On Thu, Apr 08, 2010 at 01:24:23PM -0400, Felipe Sateler wrote:
On Thu, Apr 8, 2010 at 12:50, Reinhard Tartler <siret...@tauware.de>

For jack, I think the amount of symbol files is just too much ATM. First, I'd strongly suggest to hide the symbols.

I agree here. Symbol tracking does not make sense when the signal/noise ratio is too high, as in this case.

I agree that the *switch* from 1.1.x to 1.9.x is noisy, I raised that as a concern, Reinhard have checked it out and judged it as not worrying, and I am satisfied with that.

I do not expect similar noise from here on. If more noise occur due to applied VCS patching, I would want to know, as we then might accidentally include upstream API-breaking changes too new for next upstream stable release.

And yes, if you coding experts (compared to me) consider the symbol differences between 1.1.x and 1.9.x not worrying, then I will proceed with releasing the current packaging, and postpone polishing the symbol file handling till later :-)

That's really hard to tell with that much noise. That noise also makes maintaining the symbol files in future unnecessary hard for my taste.

Painful, error-prone and superfluous. Shlibs files are enough for the relatively stable jack API, IMO.

We only _assume_ JACK API to be stable - yet we track upstream VCS so should not be certain IMO.


 - Jonas

* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to