From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A61BCC433E1 for ; Thu, 27 Aug 2020 12:58:09 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2C94522BF5 for ; Thu, 27 Aug 2020 12:58:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="eQcalZ/h" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2C94522BF5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id CBD4117D8; Thu, 27 Aug 2020 14:57:16 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz CBD4117D8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1598533086; bh=tTs2NyrNkNJCa9bwh13fEqAMipio4VYz/n8F6A5LFp4=; h=Date:From:To:Subject:In-Reply-To:References:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=eQcalZ/hWBo6YzyWcqR6uDfAlsOcwVz368OamGqOAwcefkQp3ryAWMWT+FvvwOHed P43Hy6bae133YUYZp+SiXBqnNXS5o88UVcYlqSQCRlxmEMhS5YGDnIqA9wviGUPYjZ KVHTESAfPj4okNDb40GV//76JOTKcTwCTj0QPdMc= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 5D6F2F80085; Thu, 27 Aug 2020 14:57:16 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 3C65DF8016F; Thu, 27 Aug 2020 14:57:14 +0200 (CEST) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 4BCD4F80085 for ; Thu, 27 Aug 2020 14:57:05 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 4BCD4F80085 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 3DB30B5A2; Thu, 27 Aug 2020 12:57:37 +0000 (UTC) Date: Thu, 27 Aug 2020 14:57:04 +0200 Message-ID: From: Takashi Iwai To: Takashi Sakamoto Subject: Re: [PATCH 00/25] alsa-tools: efw-downloader: add initial version of firmwre downloader for Echo Audio Fireworks devices In-Reply-To: <20200827122442.GA394751@workstation> References: <20200821073111.134857-1-o-takashi@sakamocchi.jp> <20200826093258.235615-1-o-takashi@sakamocchi.jp> <20200827122442.GA394751@workstation> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: alsa-devel@alsa-project.org, clemens@ladisch.de X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Thu, 27 Aug 2020 14:24:42 +0200, Takashi Sakamoto wrote: > > Hi, > > On Wed, Aug 26, 2020 at 01:31:53PM +0200, Takashi Iwai wrote: > > On Wed, 26 Aug 2020 11:32:58 +0200, > > Takashi Sakamoto wrote: > > > > > > Hi, > > > > > > Would I expect any reaction by maintainers of alsa-tools repository for > > > the patches? > > > > I'm reviewing those patches now. > > Thanks for your review. > > > Since it's based on meson build, it'll be tricky to include this in > > alsa-tools whether others are all autoconf. The tarball creation is > > done in the top directory and that assumes the execution of "make > > alsa-dist" in each subdirectory. Without this integration, the > > directory won't be included in the release. > > > > Could you work on it, too? > > I didn't have enough care of distributing the package. Thank you for the > indication. > > Although it's possible to write configure.ac/Makefile.am for > efw-downloader, I'd like to use meson.build for my convenience, especially > for the convenience of gnome module[1] in meson (Nowadays software in GNOME > project including GLib is mostly build by meson). > > As long as I know, the concept of release creation in GNU Autotools is > different from the one in meson build system. GNU Autotools distributes > scripts generated from Makefile.am/configure.ac and so. On the other > hand, meson distributes files maintained by git or mercurial. > > If we have a space to make enough arrangement for alsa-tools, the > top-level Makefile should be changed to have two variables for > subdirectories which includes software built by GNU Autotools and the > others, then be changed further for configure/install/alsa-dist/clean > targets. > > Nevertheless, the idea to mix all of software built by several types of > build system into one repository is not so convenient itself. I'll take > more time to investigate further for better packaging of alsa-tools. > (Tools like Android repo is a bit over-engineering in the case, mmm) > > I decline the patchset for now. OK. It's indeed awkward to mix up both auto-tools and meson. So the more suitable option would be either to modernize everything with meson, or just create a configure.ac for efw-downloader. Maybe the latter is easier, as the dependency would be only about hinawa and the check via pkgconfig is trivial even with automake. But, obviously, modernization is more appealing (with a risk of breakage, as always :) thanks, Takashi