From: "Andrey G. Grozin" <A.G.Grozin@inp.nsk.su>
To: gentoo-lisp@lists.gentoo.org
Subject: Re: [gentoo-lisp] sbcl: why not bootstrap updates from existing copies?
Date: Fri, 5 Jan 2018 12:59:12 +0700 (+07) [thread overview]
Message-ID: <alpine.LRH.2.21.1801051251190.56736@star.inp.nsk.su> (raw)
In-Reply-To: <871sj5o8lk.fsf@gmail.com>
On Thu, 4 Jan 2018, Akater wrote:
> As far as I understand, dev-lisp/sbcl ebuild unconditionally pulls
> precompiled binary and then compiles the fresh sbcl with it. Is there a
> reason why sbcl is not compiled using the existing previous copy of it?
(1) If a user installs sbcl for the first time, there is no previous copy.
(2) The previous copy (if exists) can be very old, contain bugs etc. The
build process on users' computers will be not reproducible: if some user
reports a bug, we don't know which version [s]he used for bootstrapping.
If we ask him/her, reproducing the bug still becomes more difficult: first
rebuild the urer's previous version (by the way, using which
previous-to-previous version?) and only then try to reproduce the user's
immediate problem.
Andrey
prev parent reply other threads:[~2018-01-05 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 17:08 [gentoo-lisp] sbcl: why not bootstrap updates from existing copies? Akater
2018-01-05 5:59 ` Andrey G. Grozin [this message]
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=alpine.LRH.2.21.1801051251190.56736@star.inp.nsk.su \
--to=a.g.grozin@inp.nsk.su \
--cc=gentoo-lisp@lists.gentoo.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