All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Gleb Mazovetskiy <glex.spb@gmail.com>,
	cedric.chepied@gmail.com, buildroot@buildroot.org,
	romain.tisserand@gmail.com, Peter Korsgaard <peter@korsgaard.com>
Subject: Re: [Buildroot] An issue with alsa-plugins + alsa-utils
Date: Wed, 4 Aug 2021 12:53:24 +0200	[thread overview]
Message-ID: <063f8d9b-4124-6f76-1208-0300b63df38b@mind.be> (raw)
In-Reply-To: <CADjhFRAiQKescNLz8wbeQx=+WfAA19hcLt=dbvm2XoYq6HnFMg@mail.gmail.com>



On 04/08/2021 12:12, Gleb Mazovetskiy wrote:
> Hi,
> 
> This is an issue originally reported to me by Romain Tisserand on Discord:
> 
> 1. alsa-plugins copies some files $(TARGET_DIR)/usr/share/alsa/alsa.conf.d
> 2. alsa-utils removes these files during installation ( |rm -rf
> $(TARGET_DIR)/usr/share/alsa/;|)
> 
> Cedric, can you please have a look?
> 
> I think a good option may be to not remove the |$(TARGET_DIR)/usr/share/alsa/|
> directory in alsa-utils.mk <http://alsa-utils.mk>

 Peter did the "rm -rf" 11 years ago as part of the fix for
https://bugs.buildroot.org/show_bug.cgi?id=1573
but I think the intention was just to make sure that you could unconfigure some
options, rebuild als-utils and it would leave only the configured utils. That's
a scenario that doesn't work anyway, so it's OK to remove the rm.

 Regards,
 Arnout
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

       reply	other threads:[~2021-08-04 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADjhFRAiQKescNLz8wbeQx=+WfAA19hcLt=dbvm2XoYq6HnFMg@mail.gmail.com>
2021-08-04 10:53 ` Arnout Vandecappelle [this message]
2021-08-04 11:22   ` [Buildroot] An issue with alsa-plugins + alsa-utils romain.tisserand
2021-08-04 18:00   ` Peter Korsgaard
2021-08-25 15:17     ` Gleb Mazovetskiy

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=063f8d9b-4124-6f76-1208-0300b63df38b@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=cedric.chepied@gmail.com \
    --cc=glex.spb@gmail.com \
    --cc=peter@korsgaard.com \
    --cc=romain.tisserand@gmail.com \
    /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.