From: Andy Tai <lichengtai@gmail.com>
To: help-guix@gnu.org
Subject: question on workflow for package definition development
Date: Fri, 19 Mar 2021 13:23:11 -0700 [thread overview]
Message-ID: <CAJsg1E-ZFjbH=ZCCVt6oGyzrxZbAqebjfyW9C_FiHsCotXNmfw@mail.gmail.com> (raw)
Hi, currently for updating package definitions in guix.git, these are
the steps I am following:
(from https://github.com/pjotrp/guix-notes/blob/master/INSTALL.org#building-gnu-guix-from-source-using-guix---the-bullet-proof-way)
in guix.git
guix pull
guix environment -C guix --ad-hoc bash vim guile-json
(in the new environment)
gcc --version
guile --version
rm -rf autom4te.cache/ # to be sure
make clean
./bootstrap
./configure --localstatedir=/var
make clean # to be really sure
make clean-go # to be even surer
time make -j 4
(then getting out of the special environment)
updating the relevant .scm files, testing build with
./pre-inst-env guix build -k -K <target>
etc.)
However, now every time after I do git pull in guix.git, I need to
repeat the steps above from
guix environment -C guix --ad-hoc bash vim guile-json
and make clean, re-configure, etc.. I find that just redoing make (in
the special guix environment) will not work.
Is there a way to avoid make clean and rebuilding the whole tree? I
wonder if I was missing something. Rebuilding every time is just time
consuming. Thanks for info on this
next reply other threads:[~2021-03-19 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 20:23 Andy Tai [this message]
2021-03-20 8:51 ` question on workflow for package definition development 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJsg1E-ZFjbH=ZCCVt6oGyzrxZbAqebjfyW9C_FiHsCotXNmfw@mail.gmail.com' \
--to=lichengtai@gmail.com \
--cc=help-guix@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).