alsa-utils: restore default card state handling #8662
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -26,20 +26,8 @@ post_configure_target() { | |
| } | ||
|
|
||
| post_makeinstall_target() { | ||
|
There was a problem hiding this comment. this wasnt doing anything |
||
|
There was a problem hiding this comment. do we want these WAV files? There was a problem hiding this comment. They're used by There was a problem hiding this comment. It would be preferrable to include a single .wav sample (a reduced-in-size one if possible; doesn't need to be one from the original package) and then create symlinks that recreate the appearance of having the standard files, but avoiding the bloat of actually including them. It might sound daft, but that's the ethos of a minimalist distro :) |
||
|
There was a problem hiding this comment. this file has the following contents - which are not on the LE device There was a problem hiding this comment. Not sure if this is directed to me. If it is, I'm not sure if I understand. How are they not on the device? There was a problem hiding this comment. Nothing here - where is /etc/alsa/state-daemon.conf being created? There was a problem hiding this comment. Sorry, didn't realize you were referring to There was a problem hiding this comment. Does this need to be addressed/adjusted /tuned with our planned use of alsa? (As previously this rules file was removed from the build). So when does the udev get used, versus the systemd? |
||
| mkdir -p ${INSTALL}/.noinstall | ||
| for i in aconnect amidi aplaymidi arecord arecordmidi aseqdump aseqnet; do | ||
| mv ${INSTALL}/usr/bin/${i} ${INSTALL}/.noinstall | ||
| done | ||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| # SPDX-License-Identifier: GPL-2.0-or-later | ||
|
|
||
| d /storage/.cache/alsa 0755 root root - - | ||
| L /var/lib/alsa/ - - - - /storage/.cache/alsa | ||
|
There was a problem hiding this comment. Look to using the --with-asound-state-dir option in package,mk There was a problem hiding this comment. Can do, but why? This approach, besides being simple enough, has the added benefit of retaining the standard setup as much as possible. A user familiar with ALSA on desktops for instance, needing to find the state file for whatever reason (say removing it, or trying to figure out why state is not retained), would know where to look for it. This would not be the case, if we reconfigured There was a problem hiding this comment. Have a look at prior art, e.g. openssh, where the configure option is applicable it is being used. There are not many links from / into .cache |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this wasnt doing anything