* question on workflow for package definition development
@ 2021-03-19 20:23 Andy Tai
2021-03-20 8:51 ` Ricardo Wurmus
0 siblings, 1 reply; 2+ messages in thread
From: Andy Tai @ 2021-03-19 20:23 UTC (permalink / raw)
To: help-guix
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: question on workflow for package definition development
2021-03-19 20:23 question on workflow for package definition development Andy Tai
@ 2021-03-20 8:51 ` Ricardo Wurmus
0 siblings, 0 replies; 2+ messages in thread
From: Ricardo Wurmus @ 2021-03-20 8:51 UTC (permalink / raw)
To: Andy Tai; +Cc: help-guix
Andy Tai <lichengtai@gmail.com> writes:
> guix environment -C guix --ad-hoc bash vim guile-json
You don’t need to add guile-json here. It’s part of the environment for “guix”.
> 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
One time “make clean” is quite sufficient. You don’t need to run it
twice. “make clean-go” is a subset of “make clean”, so if you already
ran the latter (twice!) then you don’t need “make clean-go”.
> 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.
I can’t remember the last time I ran “make clean”. Even “make clean-go”
is pretty rare. What does “will not work” mean?
--
Ricardo
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-03-20 8:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-19 20:23 question on workflow for package definition development Andy Tai
2021-03-20 8:51 ` Ricardo Wurmus
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).