Re: Rekindle jack implementation swapping discussion (was Re: Request to join the Debian Multimedia Team)

2010-05-31 Thread Adrian Knoth
On Sat, May 29, 2010 at 05:06:24PM -0400, Felipe Sateler wrote:

  Given the tons of C++ symbols in jackd2, I'd also suggest to make the
  jackd1 package the official dev package and also the donator of the
  symbols file.
 
 I'm quite confused by this. AFAIK, jack is a pure C API, so C++
 symbols have no place in there. 

Yep. But jackd2 is implemented in C++, and these symbols somehow are
public or leak into the symbols file (also with -fvisibility=hidden).

 However, I understood from the last discussion that those are not
 really bogus, but are some sort of internal (server-lib) API, which is
 not allowed to be used by regular clients. Is this correct?

Exactly.

 Anyway, I really think that for jack it is much better to use a shlibs
 file.

I'm completely fine with a shlibs file. Makes things a lot easier.


Cheerio

-- 
mail: a...@thur.de  http://adi.thur.de  PGP/GPG: key via keyserver

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers


Re: Rekindle jack implementation swapping discussion (was Re: Request to join the Debian Multimedia Team)

2010-05-31 Thread Felipe Sateler
On Mon, May 31, 2010 at 05:18, Adrian Knoth a...@drcomp.erfurt.thur.de wrote:
 On Sat, May 29, 2010 at 05:06:24PM -0400, Felipe Sateler wrote:

  Given the tons of C++ symbols in jackd2, I'd also suggest to make the
  jackd1 package the official dev package and also the donator of the
  symbols file.

 I'm quite confused by this. AFAIK, jack is a pure C API, so C++
 symbols have no place in there.

 Yep. But jackd2 is implemented in C++, and these symbols somehow are
 public or leak into the symbols file (also with -fvisibility=hidden).

These symbols are being explicitly exported (check the header files). See below.


 However, I understood from the last discussion that those are not
 really bogus, but are some sort of internal (server-lib) API, which is
 not allowed to be used by regular clients. Is this correct?

 Exactly.

The symbols cannot then be hidden (otherwise the server will not find
them). So they will be a noise factor _forever_. I'm wondering if this
is a correct design decision (having a single library for both a
public and a private API), but it's not my call to make. I think we
should trust upstream and just shove a libjack0.shlibs with =0.116,
and be done with it.


-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers


Rekindle jack implementation swapping discussion (was Re: Request to join the Debian Multimedia Team)

2010-05-29 Thread Eric Dantan Rzewnicki
Moving this to a new thread to make sure it gets noticed.

On Sat, May 29, 2010 at 10:08:24AM +0200, Reinhard Tartler wrote:
 On Fr, Mai 28, 2010 at 21:01:04 (CEST), Alexandre Quessy wrote:
  Hello,
  I want to join the Debian Multimedia Package Maintainers Team. (whatever
  it's called) My alioth username is alexandrequessy-guest.
 I also see that you are familiar with jack. The most pressing question
 is to if we do want to enable users to switch their jack implementation
 in squeeze. Currently that's not possible, but ideas how to rearrange
 packages, shlibs files and provides have been proposed. I have to admit
 that I've lost track and don't know if they are still being considered
 of if everyone has lost motivation to actually implement them. Perhaps
 you (or someone else) can try to pickup that discussion?
 
 I've already announced on #debian-release a few days ago that we might
 require such a transition, but we'd also need to write a more formal
 email to debian-release for that.

My current understanding is that, yes, we want it to happen. The main
issue is people who know how having the time to make it happen.

If memory serves, Adrian knows the jack code and upstream the best of
anyone here. Reinhard knows about library magic stuff from working on
ffmpeg. Jonas knows lots of cdbs magic that might be helpful.

Do any of the three of you have time in the very near future to push
this forward? 

Are there others on the team paying attention with time, interest and
knowledge not mentioned above?

For reference in case anyway is new to the discussion or needs to
review, I think most of the relevant information is in this thread:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2010-April/008854.html
 


-edrz (who can't claim to understand the details at all well, but looks
forward to learning a great deal from watching from the wings whenever
it does happen.)

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers


Re: Rekindle jack implementation swapping discussion (was Re: Request to join the Debian Multimedia Team)

2010-05-29 Thread Eric Dantan Rzewnicki
On Sat, May 29, 2010 at 02:34:45PM -0500, Gabriel M. Beddingfield wrote:

 Hi,

 On Sat, 29 May 2010, Eric Dantan Rzewnicki wrote:

 I want to join the Debian Multimedia Package Maintainers Team. (whatever
 it's called) My alioth username is alexandrequessy-guest.
 I also see that you are familiar with jack. The most pressing question
 is to if we do want to enable users to switch their jack implementation
 [snip]

 My current understanding is that, yes, we want it to happen. The main
 issue is people who know how having the time to make it happen.

 IIRC, the consensus was that the squeeze release was way too close to 
 make the drastic changes required for this to happen.  That it would need 
 to happen after that.

http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2010-April/009046.html

That contained Adrian putting his foot down to stop the debate and say:
we switch to jackd2 now. No one disagreed.

But, he went on to say we could then still try to make the swapping
possible in time for squeeze.

Maybe I misuderstood, am misremembering or missed some further
discussion.

-edrz

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers


Re: Rekindle jack implementation swapping discussion (was Re: Request to join the Debian Multimedia Team)

2010-05-29 Thread Gabriel M. Beddingfield



On Sat, 29 May 2010, Eric Dantan Rzewnicki wrote:


http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2010-April/009046.html

That contained Adrian putting his foot down to stop the debate and say:
we switch to jackd2 now. No one disagreed.

But, he went on to say we could then still try to make the swapping
possible in time for squeeze.

Maybe I misuderstood, am misremembering or missed some further
discussion.


Nope, that's right:  jack2 now.  Enable (easy) user 
switching later.


-gabriel


___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers


Re: Rekindle jack implementation swapping discussion (was Re: Request to join the Debian Multimedia Team)

2010-05-29 Thread Adrian Knoth
On Sat, May 29, 2010 at 03:55:36PM -0400, Eric Dantan Rzewnicki wrote:

  we switch to jackd2 now. No one disagreed.
  Nope, that's right:  jack2 now.  Enable (easy) user switching later.
 
 + possibly in time for squeeze, which is Reinhard's question: are we
 still going to try for it, and therefore, do we need to get a more
 detailed note to release-team (last week) about what it entails for
 coordination between this team and them.

I think it's not too hard to revive the jackd1 package, so we can at
least provide jackd1 and jackd2 in squeeze.

Given the tons of C++ symbols in jackd2, I'd also suggest to make the
jackd1 package the official dev package and also the donator of the
symbols file.

If possible, we should file a bug report against release.debian.org to
coordinate the transition, but I'm not debian-experienced enough to take
the lead.


Cheerio

-- 
mail: a...@thur.de  http://adi.thur.de  PGP/GPG: key via keyserver

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers