From: myglc2 <myglc2@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>,
Alex Vestgaard <birkeroed@protonmail.ch>
Subject: Re: GuixSD installation: binary vs source packages
Date: Sat, 25 Feb 2017 15:12:26 -0500 [thread overview]
Message-ID: <861sumav2t.fsf@gmail.com> (raw)
In-Reply-To: <20170225155236.GA3227@jasmine> (Leo Famulari's message of "Sat, 25 Feb 2017 10:52:36 -0500")
On 02/25/2017 at 10:52 Leo Famulari writes:
> On Fri, Feb 24, 2017 at 09:01:39PM -0500, myglc2 wrote:
>> In my practical experience of running a GuixSD headless server for the
>> last 12 months, if you use 'guix pull', which is effectively a rolling
>> release, there is no way to tell.
>
> The default action of `guix pull` is like a rolling release, but you can
> also use it to deploy any version or Git commit of Guix, using `guix
> pull --url=...`:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8a9cffb202414b20081910115ba76402924bdcdd
>
> You still can't be sure that we will have binary substitutes for every
> package. I just wanted to point out this little-known feature of `guix
> pull`, which gives Guix users some more flexibility without requiring
> them to maintain a Guix development environment.
Thanks. I think the issue with this feature is that there is no guidance
for picking an URL.
Here is an idea... What if hydra provided an URL guidance page? For
example, it could have a short list of "guix greatest hits URLs" for
which, hopefully, a full set of substitutes is maintained. Obvious
candidates for this list would be the last couple install images. Or, it
could provide a page ranking URLs by release date and showing substitute
coverage.
next prev parent reply other threads:[~2017-02-25 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 18:39 GuixSD installation: binary vs source packages Alex Vestgaard
2017-02-25 2:01 ` myglc2
2017-02-25 15:52 ` Leo Famulari
2017-02-25 20:12 ` myglc2 [this message]
2017-02-26 3:23 ` Leo Famulari
2017-03-06 10:59 ` Ludovic Courtès
2017-03-06 16:09 ` dian_cecht
2017-03-07 10:59 ` Ludovic Courtès
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=861sumav2t.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=birkeroed@protonmail.ch \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).