Re: [GNU-linux-libre] Replacing Yocto with Guix kernel image builds: best practices

[Begley Brothers Inc <begleybrothers@gmail.com>]

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/<packagename>`.
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/<packagename>` -
it appears other packages just drop everythin in `patches`

Appreciate any thoughts.

On Tue, May 19, 2020 at 2:09 AM Begley Brothers Inc
<begleybrothers@gmail.com> wrote:
>
> On Mon, May 18, 2020 at 5:24 AM Ricardo Wurmus <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 channel
>> > > 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 “build-resources”
>> 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’t 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 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.



-- 
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.