From debbugs-submit-bounces@debbugs.gnu.org Fri Aug 07 04:20:30 2020 Received: (at 42682) by debbugs.gnu.org; 7 Aug 2020 08:20:30 +0000 Received: from localhost ([127.0.0.1]:55631 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3xc5-0001WU-QX for submit@debbugs.gnu.org; Fri, 07 Aug 2020 04:20:30 -0400 Received: from eggs.gnu.org ([209.51.188.92]:37664) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3xc4-0001WH-4J for 42682@debbugs.gnu.org; Fri, 07 Aug 2020 04:20:28 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:38389) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k3xby-0002lG-AI; Fri, 07 Aug 2020 04:20:22 -0400 Received: from pop.92-184-100-121.mobile.abo.orange.fr ([92.184.100.121]:42824 helo=meru) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1k3xbw-00016b-Ss; Fri, 07 Aug 2020 04:20:22 -0400 From: Mathieu Othacehe To: Jan Wielkiewicz Subject: Re: [bug#42682] [PATCH 2/2] gnu: Add qmk-cli. References: <20200802204910.15356-1-tona_kosmicznego_smiecia@interia.pl> <20200802204910.15356-2-tona_kosmicznego_smiecia@interia.pl> <87y2mwt9t0.fsf@gnu.org> <20200803144349.06022fa4@interia.pl> <87o8npjvt4.fsf@gnu.org> <20200805142240.075ac063@interia.pl> Date: Fri, 07 Aug 2020 10:20:17 +0200 In-Reply-To: <20200805142240.075ac063@interia.pl> (Jan Wielkiewicz's message of "Wed, 5 Aug 2020 14:22:40 +0200") Message-ID: <87364yq33y.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 1.3 (+) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hello, > But the entire point of qmk firmware is that the user configures it. I > had to modify the source code to make my keyboard work and add some > extra features like layouts, special keys. Your solutio [...] Content analysis details: (1.3 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 3.6 RCVD_IN_SBL_CSS RBL: Received via a relay in Spamhaus SBL-CSS [92.184.100.121 listed in zen.spamhaus.org] 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record -0.0 SPF_PASS SPF: sender matches SPF record -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at https://www.dnswl.org/, medium trust [209.51.188.92 listed in list.dnswl.org] X-Debbugs-Envelope-To: 42682 Cc: 42682@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.3 (/) Hello, > But the entire point of qmk firmware is that the user configures it. I > had to modify the source code to make my keyboard work and add some > extra features like layouts, special keys. Your solution will only work > for the unmodified and default firmware, or is there a Guix solution > for it I'm not aware of, like a convenient interface for user defined > packages? Oh I see. Nonetheless, qmk_cli is a thin wrapper around qmk_firmware. I think it would make more sense to have qmk_firmware properly packaged. This way we would offer people a way to build their customized firmware without propagating toolchains and fetching a git repository. WDYT? Mathieu