From: Ricardo Wurmus <rekado@elephly.net>
To: Sahithi Yarlagadda <sahi@swecha.net>
Cc: 30894@debbugs.gnu.org
Subject: [bug#30894] Submission of patch for Add r-abc
Date: Thu, 29 Mar 2018 12:32:25 +0200 [thread overview]
Message-ID: <87lgebdveu.fsf@elephly.net> (raw)
In-Reply-To: <6c9c531d-75a5-be08-2784-ebae3c3a432b@swecha.net>
Hi Sahithi,
> 1) Cloning the Source
>
> 2) Running guix environment guix
>
> 3) ./bootstrap
>
> 4) ./configure --localstatedir=/var
You need to perform these steps only once.
> 5) make
>
> 6) Make Changes to the cran.scm file
>
> 7) Build using ./pre-inst-env guix build <package>
>
> 8) If build is success, format the patch and submit the patch
I suggest running make again after making changes to any file in the
Guix source tree. This way you can avoid the “.go file is older than
the .scm” messages.
> *When i am planning to write a different package description, i am
> following this*
>
> 9) rebasing the patch
>
> 10) Pull for any changes
>
> 11) running the process from (2)
I’d do this instead:
git fetch origin # fetch any upstream changes
git stash # hide my uncommitted local changes
git rebase origin/master # rebase my local commits on top of upstream
git stash pop # apply my uncommitted local changes
make # compile .scm to .go
Note that you should be inside of a suitable environment when running
“make”, so better do all of this after “guix environment guix”.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-03-29 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 11:14 [bug#30894] Submission of patch for Add r-abc Sahithi Yarlagadda
2018-03-21 21:27 ` Ricardo Wurmus
2018-03-28 19:44 ` Ricardo Wurmus
2018-03-29 10:15 ` Sahithi Yarlagadda
2018-03-29 10:32 ` Ricardo Wurmus [this message]
2018-03-29 10:50 ` Sahithi Yarlagadda
2018-03-29 11:00 ` Sahithi Yarlagadda
2018-03-29 11:28 ` Sahithi Yarlagadda
2018-04-02 21:26 ` bug#30894: " Ricardo Wurmus
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=87lgebdveu.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=30894@debbugs.gnu.org \
--cc=sahi@swecha.net \
/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.