All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Vroon <tony@linx.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA package release v1.0.26 (user space)
Date: Fri, 07 Sep 2012 14:26:01 +0100	[thread overview]
Message-ID: <5049F5E9.2090507@linx.net> (raw)
In-Reply-To: <s5htxvaufvp.wl%tiwai@suse.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/09/12 14:22, Takashi Iwai wrote:
> I'm not sure about alsa-headers, though.  Isn't it a package 
> containing header files from alsa-lib?

We generate only our headers from alsa-driver, and don't use the
actual drivers in there (favouring the kernel for that). If you're
saying that the same headers can be stolen from the alsa-lib tarball
instead that would be delightful.
I shall have a proper look at this over the weekend or on Monday, and
if I can come up with a good reason as to why that wouldn't work I'll
share it with you.

In all honesty I inherited ebuild scripts that worked like this and
haven't had the need to revise that until now.

Regards,
- -- 
Tony Vroon
Server systems manager
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBJ9ekACgkQp5vW4rUFj5qhpQCfSmctWhcqY2FpKqPmcAV18+DX
zhwAnihPe26oXXBAF1L4T9KzxmAemIn5
=GwOC
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-09-07 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 12:19 ALSA package release v1.0.26 (user space) Jaroslav Kysela
2012-09-07 13:11 ` Tony Vroon
2012-09-07 13:22   ` Takashi Iwai
2012-09-07 13:26     ` Tony Vroon [this message]
2012-09-07 13:28       ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5049F5E9.2090507@linx.net \
    --to=tony@linx.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.