From: Roman Inflianskas <infroma@gmail.com>
To: help-guix@gnu.org
Subject: Guix + User Namespaces wrapper (UGuix)
Date: Sat, 6 Feb 2021 16:25:17 +0200 [thread overview]
Message-ID: <CAB3qpweGdLz7QaNy7c8L6jFzpu0jTkUFk=fCP7pOpyu4J2dfpQ@mail.gmail.com> (raw)
Hello,
I'm writing a wrapper for Guix + User Namespaces called UGuix. The goal is
to implement a tool that would be easy to use and that would provide users
a possibility to install Guix, and then Guix packages without having a
root. It's inspired by https://github.com/nix-community/nix-user-chroot but
aims to be more user-friendly and high-level.
It already works like this:
```
$ ug bootstrap
... # Downloads the binary distribution of Guix, unpacks it to
`~/.guix/root`, does unshare + chroot to the dir with `/gnu` mounted along
with all `/` contents, auths substitutes, downloads latest packages,
installs `hello`
Hello, world!
$ ug run hello # Runs `hello` installed to `~/.guix/root/gnu`
Hello, world!
$ ug guix install mc
... # Installs mc
```
It works but I want to want to do proper testing before I publish my work.
The question is: is it OK to run the tests which run bootstrap with
downloading packages from substitutes over and over again? Also, I want to
make it so that GitHub Actions will start the tests on new PRs.
--
Regards, Roman Inflianskas
next reply other threads:[~2021-02-06 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 14:25 Roman Inflianskas [this message]
2021-02-06 15:02 ` Guix + User Namespaces wrapper (UGuix) Pierre Neidhardt
2021-02-24 14:21 ` Ricardo Wurmus
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='CAB3qpweGdLz7QaNy7c8L6jFzpu0jTkUFk=fCP7pOpyu4J2dfpQ@mail.gmail.com' \
--to=infroma@gmail.com \
--cc=help-guix@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.
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).