From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id YAVqDXSGw15degAA0tVLHw (envelope-from ) for ; Tue, 19 May 2020 07:10:44 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id qOhvCXSGw150AwAAbx9fmQ (envelope-from ) for ; Tue, 19 May 2020 07:10:44 +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 8A020940712 for ; Tue, 19 May 2020 07:10:43 +0000 (UTC) Received: from localhost ([::1]:46200 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jawOg-0000rR-GJ for larch@yhetil.org; Tue, 19 May 2020 03:10:42 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:43058) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jawOX-0000r8-VI for guix-devel@gnu.org; Tue, 19 May 2020 03:10:33 -0400 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]:42196) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jawOW-0005mL-2S for guix-devel@gnu.org; Tue, 19 May 2020 03:10:33 -0400 Received: by mail-lj1-x22e.google.com with SMTP id d21so12516461ljg.9 for ; Tue, 19 May 2020 00:10:31 -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 :cc; bh=sC8InhYA2vRwgtB+vcauIF5GVNdhyji5bBGdkwfp3iE=; b=jMtynipA0H3T/dFzKJ0n0kbHlXF2bjouzS9y/+CLpl+fIQRpAK+TcthjU739pgUt5n lljhd4yPDunouu1RQ3EdZgqXEa8A4dcBrPFemRFk9gsxfvG6qCpsODl79sUdbzev8tE1 w3oQA7uoBF5kO4tqngtWE9FVvufaCVjYgSRHOc5IzugyLGAdJYTtlAhOxc+Dd/PvndBp frt4kY4Yqc5jHXEUjKil92QTiAMJDkq8rXQmL7WT8kZZJSI66Gj3qHjGbZ4ySYTcCFjJ 5hIYdsrT/KEIFQ9IXWDpCT5WFjKG6PVg7aUIKnUgsmn970BcXOd4/3ZfTbRS7+tc1LXt SQ+w== 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:cc; bh=sC8InhYA2vRwgtB+vcauIF5GVNdhyji5bBGdkwfp3iE=; b=qtbU3lwcLPR9L5dZSPjabyx07icmaF9zXiC5oIc9UYZ0DqqWcFQXnneLnRE2q3ubof 10wVKjZ5O/bWTrLGpvKw6KZNiFVbRWaOnpsatS32dbelifvTEt0U3f83+jQrd2We379Y zfncYckY+A3Hq+lDQutyiq/ETAVBp6Wp3rgt21mLThVhAekkCKkghYkXuPgBHTH51O68 X95xkgXjM2VvyO4LgS4hn3ylfdslxgfGl8TEwv8m3Beoi4lDAaw92oQSa4LKevlTuPti LNcsWr7qkmNMABULULzMJBZ0Vea5HyYOMw302Qoe+Me8VbGy4fmoGEUWdnG5w2tx4xt5 ZXSQ== X-Gm-Message-State: AOAM533EjBDGFnPMHm8WPHmNB24gs+SEhxN7FgKEWgU30xgbnVz22eXX SJIdAF6/y/CpIwMYzWwjpZ2sH4nGQXhSkFDjqoo= X-Google-Smtp-Source: ABdhPJwSASfPlvXI1UZ564s5RDWnUS6V4nMQPMKhQcUsvf+/1uA2KetANdVgIRu16+9K1fm6xdKvUb4PvOAVXv5QS1s= X-Received: by 2002:a2e:89cb:: with SMTP id c11mr8343832ljk.97.1589872229763; Tue, 19 May 2020 00:10:29 -0700 (PDT) MIME-Version: 1.0 References: <87lflqhgad.fsf@elephly.net> <874ksdh77a.fsf@elephly.net> In-Reply-To: <874ksdh77a.fsf@elephly.net> From: Begley Brothers Inc Date: Tue, 19 May 2020 02:09:53 -0500 Message-ID: Subject: Re: [GNU-linux-libre] Replacing Yocto with Guix kernel image builds: best practices To: Ricardo Wurmus Content-Type: multipart/alternative; boundary="0000000000007e4f1e05a5faf978" Received-SPF: pass client-ip=2a00:1450:4864:20::22e; envelope-from=begleybrothers@gmail.com; helo=mail-lj1-x22e.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, HTML_MESSAGE=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: , Cc: guix-devel 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=jMtynipA; 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: 2aR7dI8O4/7X --0000000000007e4f1e05a5faf978 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 and > add > > > that to > > > the native inputs, or you can include the config files in your channe= l > > > 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-resou= rces=E2=80=9D > as a native-input, which is an SVN origin. > Thanks Ricardo, That was great - I expected external linkages like that to be rejected for inclusion in upstream, so it is nice to see - I think that approach 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. --=20 Kind Regards Begley Brothers Inc. 1. *The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share a= ny 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 mista= ke does not occur in the future.* 2. *This message has been sent as a part of discussion between Begley Brothers Inc. and the addressee whose name is specified above. Should yo= u receive this message by mistake, we would be most grateful if you inform= ed 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.* 3. *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 b= e ensured as, despite our efforts, the data included in emails could be infected, intercepted, or corrupted. Therefore, the recipient should che= ck the email for threats with proper software, as the sender does not accep= t liability for any damage inflicted by viewing the content of this email.= * 4. *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 n= ot take any liability for such statements included in emails. In case of an= y damages or other liabilities arising, employees are fully responsible fo= r the content of their emails.* --0000000000007e4f1e05a5faf978 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, May 18, 2020 at 5:24 AM Ricardo W= urmus <rekado@elephly.net> = wrote:

Begley Brothers Inc <begleybrothers@gmail.com> writes:

> > You can either put your config files in a separate git repository= and add
> > that to
> > the native inputs, or you can include the config files in your ch= annel
> > repository (or later in Guix itself).
> >
>
> Thanks for the suggestion.=C2=A0 That gives some assurance.
> Could you point to an existing guix (upstream) package that is a best<= br> > 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.=C2=A0 One example is
java-cisd-args4j in gnu/packages/java.scm, which has =E2=80=9Cbuild-resourc= es=E2=80=9D
as a native-input, which is an SVN origin.

<= div>Thanks Ricardo, That was great - I expected external linkages like that= to be
rejected for inclusion in upstream, so it is nice to see -= I think that approach=C2=A0
gives us a fallback in case our pref= erred approach does not work out.
=C2=A0
> Can "add it to their ~/.config/guix/channels.scm file" be sc= ripted as part
> of the
> package?
> Is there an example of a guix (upstream) package that does this?

No, channel configuration is a user action.=C2=A0 The channel would be the<= br> 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.

  1. The content of this email is confidential and intended for t= he=20 recipient specified in message only. It is strictly forbidden to share=20 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.
  2. This message has be= en sent as a part of discussion between Begley Brothers Inc. and the addres= see whose name is specified above. Should=20 you receive this message by mistake, we would be most grateful if you=20 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=20 it or any part of it to anyone else. Thank you for your cooperation and=20 understanding.
  3. Begley Brothers Inc. = puts the security of the client at a high priority.=20 Therefore, we have put efforts into ensuring that the message is error=20 and virus-free. Unfortunately, full security of the email cannot be=20 ensured as, despite our efforts, the data included in emails could be=20 infected, intercepted, or corrupted. Therefore, the recipient should=20 check the email for threats with proper software, as the sender does not accept liability for any damage inflicted by viewing the content of=20 this email.
  4. The views and opinions included in this email = belong to their author and do not necessarily mirror the views and opinions of the company.=20 Our employees are obliged not to make any defamatory clauses, infringe,=20 or authorize infringement of any legal right. Therefore, the company=20 will not take any liability for such statements included in emails. In=20 case of any damages or other liabilities arising, employees are fully=20 responsible for the content of their emails.
--0000000000007e4f1e05a5faf978--