All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Gleb Mazovetskiy <glex.spb@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/alsa-utils: Fix alsa-plugins compatibility
Date: Tue, 07 Sep 2021 12:07:31 +0200	[thread overview]
Message-ID: <87sfygg0m4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210825151659.59671-1-glex.spb@gmail.com> (Gleb Mazovetskiy's message of "Wed, 25 Aug 2021 16:16:59 +0100")

>>>>> "Gleb" == Gleb Mazovetskiy <glex.spb@gmail.com> writes:

 > Previously, alsa-plugins would not work if alsa-utils was installed
 > after it. This happened because:

 > 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/;)

 > The `rm -rf` command was originally added as part of the fix for
 > https://bugs.buildroot.org/show_bug.cgi?id=1573 11 years ago.

 > The intention might have been to allow for unconfiguring some options
 > and then rebuilding alsa-utils. However, this is a scenario that does
 > not work anyway.

 > The simplest fix for the `alsa-plugins` compatibility issue appears to
 > be to remove the `rm -rf` command.

 > Signed-off-by: Gleb Mazovetskiy <glex.spb@gmail.com>

Committed to 2021.02.x and 2021.05.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2021-09-07 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 15:16 [Buildroot] [PATCH 1/1] package/alsa-utils: Fix alsa-plugins compatibility Gleb Mazovetskiy
2021-08-25 20:13 ` Arnout Vandecappelle
2021-09-07 10:07 ` Peter Korsgaard [this message]

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=87sfygg0m4.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --cc=glex.spb@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.