[alsa-devel] alsa-ucm-conf repository - initial import

[alsa-devel] alsa-ucm-conf repository - initial import

[Jaroslav Kysela]

Hello all,

  I just made an initial import to to alsa-ucm-conf repository which is in the
'import' branch:

  https://github.com/alsa-project/alsa-ucm-conf/tree/import

  I do not have the BSD-3-Clause licence acknowledgements from some minor
contributors. I do not think that it's a problem. I would expect that if we do
not have a disagreement, it is fine.

  The question is, if we need automake/autoconf tools to package those files.
It seems to me that it might be clever to keep this ASIS for now.
Users/packagers can just do 'cp' to the appropriate directory.

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: [alsa-devel] alsa-ucm-conf repository - initial import

[Mark Brown]

[-- Attachment #1.1: Type: text/plain, Size: 453 bytes --]

On Tue, Sep 24, 2019 at 02:45:31PM +0200, Jaroslav Kysela wrote:

>   The question is, if we need automake/autoconf tools to package those files.
> It seems to me that it might be clever to keep this ASIS for now.
> Users/packagers can just do 'cp' to the appropriate directory.

I guess the only advantage would be that it'd tell people what
the expected directory was but otherwise yeah, I don't see a
pressing need to have the makefiles and whatnot.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel