From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id UAvEHNuPw15TZwAA0tVLHw (envelope-from ) for ; Tue, 19 May 2020 07:50:51 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id UCaZGNuPw17SJgAA1q6Kng (envelope-from ) for ; Tue, 19 May 2020 07:50:51 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 1BE6F940B6B for ; Tue, 19 May 2020 07:50:51 +0000 (UTC) Received: from localhost ([::1]:60282 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jax1W-000713-3E for larch@yhetil.org; Tue, 19 May 2020 03:50:50 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:48044) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jax1N-00070t-FX for guix-devel@gnu.org; Tue, 19 May 2020 03:50:41 -0400 Received: from mail-lf1-x141.google.com ([2a00:1450:4864:20::141]:44315) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jax1M-0007Ee-Gi for guix-devel@gnu.org; Tue, 19 May 2020 03:50:41 -0400 Received: by mail-lf1-x141.google.com with SMTP id w15so3026733lfe.11 for ; Tue, 19 May 2020 00:50:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=CiwSQhJ6N+r6i7DvM1AeoHoXi/vc+nron2M0rf6WXrI=; b=akgxVfwP+YhAgSefJTKrD67KpBA5WB4Fdi6eCxk/f5hIiwOvXNNYT117QygKpHF041 DZwJA3gkP6Bu+qslPfNB8mgWDFmHEYJRUn5Kdur4MzL3ahI/b6qIJyp7BYG8N73JBDTV qaDA4f1NQEJehIOhIlHe6zOmhiSvEy/xLm91mnWodQ5f8VY55zmqb1xfMtvQBSPRb200 YQ5/gA/JRy5Uh/uySNUfL+dMiZTyGaiM9fZm1ObsTAXu/IiNF7Wfg3p2PwAkQi/FQAdB EV1neOjNgG6mWkVS/ClhJqTtG+0HpI3RupqrQvWgXFSWdAXGnxDeAcKB8FKnS1FFjP6i gJdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=CiwSQhJ6N+r6i7DvM1AeoHoXi/vc+nron2M0rf6WXrI=; b=p7ur+DRBVMERb8qF1hO24YnrbN3i2k8l6RtciBbXgY5596rxchf8Gki7r0mwWCyVDG l6bi0Z9UDoiqTr2MXNZRI7RjrTO5JqHAEuFwckDFc67mt6q75TFu0RvhnEWUGLzZKiKe cMpEcK+Hzt6QIeAyqBpAqCeM7jKJZCOzD9toduFkZmj7YbDGPQKrrRpP8Xbklt9YlSzI B7gcrw8oO14wH7NKLJmYWjcLikhqbDhg/kL4xxqJx+v+47UuqGoCmrcY+mn7UowbUbA1 XOUh0EeW8g5I0ZWbUc/ahKPU844YNbQS5QBMFAIkXHozZFooDdUxIE1Lxwo+QV5KED/n X2aQ== X-Gm-Message-State: AOAM533LfvDb5aKLAZYoAbI4RFcodiySiFb72ipszYHqeoyEEin9gPv2 Kbtd+ho5BhvVcBSFrCJ36+j3lJjsVbOM9IdPmKgN6Z+ZSXM= X-Google-Smtp-Source: ABdhPJypCLBn0GFMLMLBtrxfcVyvP3XO4tK7qyNJtP7E13XjXyW8uKqwxKQyOnZNnPuh5xxDkr2V5nJERjKutbiZCxE= X-Received: by 2002:a05:6512:10c8:: with SMTP id k8mr413503lfg.181.1589874638215; Tue, 19 May 2020 00:50:38 -0700 (PDT) MIME-Version: 1.0 References: <87lflqhgad.fsf@elephly.net> <874ksdh77a.fsf@elephly.net> In-Reply-To: From: Begley Brothers Inc Date: Tue, 19 May 2020 02:50:01 -0500 Message-ID: Subject: Re: [GNU-linux-libre] Replacing Yocto with Guix kernel image builds: best practices To: guix-devel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::141; envelope-from=begleybrothers@gmail.com; helo=mail-lf1-x141.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=akgxVfwP; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -1.71 X-TUID: lqUp168nTl6y Hi, Thanks for all the thoughtful input. We think we have worked out a preferred path - ironically from a closer reading of the linux.scm - once we had some familiarity with Guile. We think (with doubts we'll elaborate on): 1. All config files and any such files should go in a folder `gnu/packages/aux-files/`. 2. All patches should go in `gnu/packages/patches` where they all seem to live at the toplevel. The doubts are: Is this is the 'correct' way going forward - it appears only three packages adopt this location. Are we able to store patches in `gnu/packages/patches/` - it appears other packages just drop everythin in `patches` Appreciate any thoughts. On Tue, May 19, 2020 at 2:09 AM Begley Brothers Inc wrote: > > On Mon, May 18, 2020 at 5:24 AM Ricardo Wurmus wrote= : >> >> >> Begley Brothers Inc writes: >> >> > > You can either put your config files in a separate git repository an= d add >> > > that to >> > > the native inputs, or you can include the config files in your chann= el >> > > repository (or later in Guix itself). >> > > >> > >> > Thanks for the suggestion. That gives some assurance. >> > Could you point to an existing guix (upstream) package that is a best >> > practice >> > example of each of those two approaches? >> > - accessing files from a separate repo >> > - a guix (upstream) package using other files >> >> There are many examples in the Guix repository. One example is >> java-cisd-args4j in gnu/packages/java.scm, which has =E2=80=9Cbuild-reso= urces=E2=80=9D >> as a native-input, which is an SVN origin. > > > Thanks Ricardo, That was great - I expected external linkages like that t= o be > rejected for inclusion in upstream, so it is nice to see - I think that a= pproach > gives us a fallback in case our preferred approach does not work out. > >> >> > Can "add it to their ~/.config/guix/channels.scm file" be scripted as = part >> > of the >> > package? >> > Is there an example of a guix (upstream) package that does this? >> >> No, channel configuration is a user action. The channel would be the >> thing that provides your package in the first place. >> >> But since you want to add your package variants to Guix itself a >> discussion of channels isn=E2=80=99t really interesting. > > > Agreed. > > Thanks again. > > -- > Kind Regards > > Begley Brothers Inc. > > The content of this email is confidential and intended for the recipient = specified in message only. It is strictly forbidden to share any part of th= is message with any third party, without a written consent of the sender. I= f you received this message by mistake, please reply to this message and fo= llow with its deletion, so that we can ensure such a mistake does not occur= in the future. > This message has been sent as a part of discussion between Begley Brother= s Inc. and the addressee whose name is specified above. Should you receive = this message by mistake, we would be most grateful if you informed us that = the message has been sent to you. In this case, we also ask that you delete= this message from your mailbox, and do not forward it or any part of it to= anyone else. Thank you for your cooperation and understanding. > Begley Brothers Inc. puts the security of the client at a high priority. = Therefore, we have put efforts into ensuring that the message is error and = virus-free. Unfortunately, full security of the email cannot be ensured as,= despite our efforts, the data included in emails could be infected, interc= epted, or corrupted. Therefore, the recipient should check the email for th= reats with proper software, as the sender does not accept liability for any= damage inflicted by viewing the content of this email. > The views and opinions included in this email belong to their author and = do not necessarily mirror the views and opinions of the company. Our employ= ees are obliged not to make any defamatory clauses, infringe, or authorize = infringement of any legal right. Therefore, the company will not take any l= iability for such statements included in emails. In case of any damages or = other liabilities arising, employees are fully responsible for the content = of their emails. --=20 Kind Regards Begley Brothers Inc. The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. This message has been sent as a part of discussion between Begley Brothers Inc. and the addressee whose name is specified above. Should you receive this message by mistake, we would be most grateful if you informed us that the message has been sent to you. In this case, we also ask that you delete this message from your mailbox, and do not forward it or any part of it to anyone else. Thank you for your cooperation and understanding. Begley Brothers Inc. puts the security of the client at a high priority. Therefore, we have put efforts into ensuring that the message is error and virus-free. Unfortunately, full security of the email cannot be ensured as, despite our efforts, the data included in emails could be infected, intercepted, or corrupted. Therefore, the recipient should check the email for threats with proper software, as the sender does not accept liability for any damage inflicted by viewing the content of this email. The views and opinions included in this email belong to their author and do not necessarily mirror the views and opinions of the company. Our employees are obliged not to make any defamatory clauses, infringe, or authorize infringement of any legal right. Therefore, the company will not take any liability for such statements included in emails. In case of any damages or other liabilities arising, employees are fully responsible for the content of their emails.