From: David Seaward <dseaward925@gmail.com>
To: guix-devel@gnu.org
Subject: Updating Guix package manager on Debian-based systems
Date: Tue, 03 Oct 2017 10:24:07 -0000 [thread overview]
Message-ID: <E-CPNv985fJnprBvHVvgaXKpNoezrpFk8UpyBiFCNQ2211@mailpile> (raw)
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
Hi all,
Previous discussion suggested that Guix (the package manager)
could not be included in Debian (and therefore derivatives) due
to technical policy. As a Debian-derivative user (PureOS and
sometimes Ubuntu) I'd still like a convenient way to try out and
recommend Guix to others. That is, more convenient than the (very
thorough) instructions at
https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.html
I think this hinges on how to get updates once Guix is installed.
If Guix can perform updates itself (including system
re-configuration as required), then a one-off first-time script
for Debian-based systems would be sufficient. I'm going to
(slowly) try my hand at this as time permits.
But, if Guix can't update itself or can't perform configuration
changes on a parent Debian system (should the need arise), then a
deb package is definitely more suitable. Delivering it in a deb
repository (rather than just offering a deb file to download)
would be best, because then users would get updates easily. For
the user it would be as simple as this...
sudo add-apt-repository 'deb https://magical.unicorn/repos/guix
stable main'
# maybe some command here for a key
sudo apt update
sudo apt install guix
Of course, someone would need to keep packaging guix as a deb,
build the debs and push them to https://magical.unicorn/repos --
it wasn't clear to me if this kind of effort is feasible?
Regards,
David
next reply other threads:[~2017-10-03 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 10:24 David Seaward [this message]
2017-10-04 14:25 ` Updating Guix package manager on Debian-based systems Ludovic Courtès
2017-10-08 15:38 ` Adonay Felipe Nogueira
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=E-CPNv985fJnprBvHVvgaXKpNoezrpFk8UpyBiFCNQ2211@mailpile \
--to=dseaward925@gmail.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.