all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: L p R n d n <guix@lprndn.info>, guix-devel@gnu.org
Subject: Re: First patch & hello
Date: Wed, 14 Nov 2018 20:07:20 +0100	[thread overview]
Message-ID: <bd93886c-740a-9fe8-0c9d-595cfc016c98@riseup.net> (raw)
In-Reply-To: <10edc45bbfff91735097e6af9f214d9d@posteo.net>

Hi :)

Welcome to the community.

On 2018-11-14 16:51, L p R n d n wrote:
> Ricardo Wurmus <rekado@elephly.net> writes:

snip

> 
> Do you know why it wasn't added? I used magit format-patch.

I did not get to learn magit yet. Did you commit first?

I commit first and then format-patch. (with the git CLI)

> 

snip

> 
> Is there a way to specify a custom location for "guix lint"? A little
> bit like the "-L" option from "guix build" for example?
> I suppose the right way to invoke 'guix lint' should be to use 
> "./pre-inst-env" in a local
> guix repository, but I didn't find where I was supposed to find it. :/

this script is generated by bootstrapping and configuring the source of 
guix.
(We should really note this in the manual. I stumbled on the same stone 
a year ago. I will prepare a patch).
you can specify a package as argument to guix lint.
"guix lint <package-name>"

> 
>> Could you please send an updated patch to guix-patches@gnu.org?
>>
> 
> I will soon. I just tested to build the package with "rounds=2" and it
> seems the package isn't deterministic. Is it acceptable or a total
> no-go?

Submit it after linting it and others can help you to find the cause of 
this. (usually timestamp inflicted)

-- 
Cheers
Swedebugia

  reply	other threads:[~2018-11-14 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 17:35 First patch & hello L p R n d n
2018-11-14 12:04 ` Ricardo Wurmus
2018-11-14 15:51   ` L p R n d n
2018-11-14 19:07     ` swedebugia [this message]
2018-11-14 19:58     ` Ricardo Wurmus
2018-11-15 23:08       ` L p R n d n

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bd93886c-740a-9fe8-0c9d-595cfc016c98@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=guix@lprndn.info \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.