From: David Pirotte <david@altosw.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Creating a reliable bootstrap for building from source
Date: Sun, 14 May 2017 22:20:29 -0300 [thread overview]
Message-ID: <20170514222029.3e17ffc0@capac> (raw)
In-Reply-To: <87shk7qg4p.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
Heya,
> As a user I want something like ‘apt-get update’, which is what ‘guix
> pull’ tries to do.
For end-users, cool stuff would be:
nguix [ guix-ncurse
u [ update the aptitude cached list of all packages,
[ installed or not... just package descriptions, nothing
[ has been downloaded yet
U [ mark as 'wish to update'
g [ list the above marked for update packages, then fine tune
[ using =, -, + ...
g ok, download what I really selected to be updated
and update...
note that the most important aptitude ncurse menu is 'Cancel pending
actions' :)
or using emacs, 'à la magit'
M-x guix-status
u
U
...
> For Guix developers, I think it’s reasonable to have a traditional GNU
> build system. After all, Guix is also a regular software package that
> people can build from source with “./configure && make && make install”.
If I could just grab guile-gnutls and “./configure && make && make install”
then I could compile, play, use, learn, contribute with/to guix...
Cheers,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-05-15 1:21 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 16:13 Ready for Guile 2.2! Ludovic Courtès
2017-03-15 20:33 ` Pjotr Prins
2017-03-15 20:41 ` Ludovic Courtès
2017-04-20 12:35 ` Ludovic Courtès
2017-04-20 13:10 ` Andy Wingo
2017-04-20 15:21 ` Maxim Cournoyer
2017-04-21 16:05 ` Joshua Branson
2017-04-22 22:20 ` Ludovic Courtès
2017-04-21 21:03 ` Ludovic Courtès
2017-04-24 1:31 ` Maxim Cournoyer
2017-04-21 21:14 ` Ludovic Courtès
2017-03-31 16:34 ` Ludovic Courtès
2017-04-22 22:34 ` ‘guix pull’ vs. transition to Guile 2.2 Ludovic Courtès
2017-04-23 14:09 ` Jan Nieuwenhuizen
2017-04-27 13:25 ` Ludovic Courtès
2017-05-09 21:22 ` Heads-up: " Ludovic Courtès
2017-05-09 22:26 ` myglc2
2017-05-10 12:05 ` Ludovic Courtès
2017-05-10 17:11 ` myglc2
2017-05-11 0:40 ` myglc2
2017-05-11 8:29 ` Ludovic Courtès
2017-05-11 8:50 ` Vincent Legoll
2017-05-11 20:53 ` Ludovic Courtès
2017-05-11 11:53 ` myglc2
2017-05-11 17:48 ` ng0
2017-05-11 18:17 ` ng0
2017-05-11 20:49 ` Adonay Felipe Nogueira
2017-05-12 8:11 ` Chris Marusich
2017-05-18 12:32 ` ng0
2017-05-14 13:50 ` Pjotr Prins
2017-05-14 15:35 ` Pjotr Prins
2017-05-14 16:13 ` Pjotr Prins
2017-05-14 16:28 ` Jan Nieuwenhuizen
2017-05-14 17:29 ` pjotr.public12
2017-05-14 18:30 ` Creating a reliable bootstrap for building from source Pjotr Prins
2017-05-14 21:32 ` Ludovic Courtès
2017-05-15 1:20 ` David Pirotte [this message]
2017-05-15 13:27 ` Ludovic Courtès
2017-05-15 7:35 ` Pjotr Prins
2017-05-15 13:28 ` Ludovic Courtès
2017-05-17 7:47 ` Pjotr Prins
2017-05-19 8:58 ` Ludovic Courtès
2017-05-17 7:52 ` Pjotr Prins
2017-05-14 21:28 ` Heads-up: transition to Guile 2.2 Ludovic Courtès
2017-05-15 7:26 ` Pjotr Prins
2017-05-15 15:48 ` Ludovic Courtès
2017-05-15 20:24 ` Rethinking guix pull [was Re: Heads-up: transition to Guile 2.2] myglc2
2017-05-16 15:55 ` Ricardo Wurmus
2017-05-16 20:56 ` Maxim Cournoyer
2017-05-18 13:54 ` Katherine Cox-Buday
2017-05-18 15:08 ` Ludovic Courtès
2017-05-17 12:45 ` Ludovic Courtès
2017-05-17 17:54 ` myglc2
2017-05-17 16:06 ` myglc2
2017-05-17 17:46 ` myglc2
2017-05-17 23:45 ` Leo Famulari
2017-05-12 5:41 ` ‘guix pull’ vs. transition to Guile 2.2 Chris Marusich
-- strict thread matches above, loose matches on Subject: below --
2017-05-14 19:54 Creating a reliable bootstrap for building from source Jeremiah
2017-05-14 21:17 ` Pjotr Prins
2017-05-15 0:11 Jeremiah
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=20170514222029.3e17ffc0@capac \
--to=david@altosw.be \
--cc=guix-devel@gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).