unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>,
	Pjotr Prins <pjotr.public12@thebird.nl>
Subject: Re: “Guix Profiles in Practice”
Date: Sun, 27 Oct 2019 03:56:52 -0500	[thread overview]
Message-ID: <20191027085652.75yygzkf3vttcpjz@thebird.nl> (raw)
In-Reply-To: <87lft7lt84.fsf@ambrevar.xyz>

On Sat, Oct 26, 2019 at 12:02:51PM +0200, Pierre Neidhardt wrote:
> Pjotr Prins <pjotr.public12@thebird.nl> writes:
> 
> > On Fri, Oct 25, 2019 at 12:36:01PM -0400, Thompson, David wrote:
> >> On Fri, Oct 25, 2019 at 6:57 AM Ludovic Courtès <ludo@gnu.org> wrote:
> >> >
> >> > Hello Guix!
> >> >
> >> > Here’s a new blog post by Pierre Neidhardt entitled “Guix Profiles in
> >> > Practice”:
> >> >
> >> >   https://guix.gnu.org/blog/2019/guix-profiles-in-practice/
> >> >
> >> > A great discussion on the benefits of manifests and on ways to manage
> >> > several profiles!
> >> 
> >> Great article!
> >
> > I agree. One useful thing not mentioned in there is, that before
> > loading a profile, it may be worthwhile to empty the shell with
> >
> >   env -i /bin/bash --login --noprofile --norc
> >
> >   . ~/opt/my-tools-profile/etc/profile
> >
> > so no existing shell variables may pollute your beautiful setup. 
> 
> Nice tip, Pjotr!
> 
> We can add it to the cookbook.  Shall I add it to the blog article now
> that it's published?

Why not?

> In https://lists.gnu.org/archive/html/guix-devel/2019-10/msg00565.html
> we discussed the possibility to remove a specific profile from the
> environment, which would be a more general version of what you propose.
> It currently has some shortcomings, but maybe we can fix them.

Sounds great.

Pierre, we have the minimalistic and emerging languages devroom at
FOSDEM this year. I am thinking we could do a talk about using Guix as
a development environment. I mean profiles are great for development -
I use them all the time, including guix environment -C. That could be
a talk.

Another talk could be about programming Guix from the REPL. Guix as a
DSL if you will. Anyone interested in doing a talk about that?

BTW I am also starting to use rash - the racket shell and we have
gash. Anyone want to talk about that? We should invite the authors.

Pj

  reply	other threads:[~2019-10-27  8:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 10:24 “Guix Profiles in Practice” Ludovic Courtès
2019-10-25 16:36 ` Thompson, David
2019-10-25 20:44   ` Pjotr Prins
2019-10-26 10:02     ` Pierre Neidhardt
2019-10-27  8:56       ` Pjotr Prins [this message]
2019-10-27 11:30         ` Pierre Neidhardt
2019-10-27 11:43           ` Hartmut Goebel
2019-10-27 20:06           ` Konrad Hinsen
2019-10-27 21:05             ` Pierre Neidhardt
2019-10-28 16:20               ` Konrad Hinsen
2019-10-30  8:36     ` Pierre Neidhardt
2019-10-26  0:34   ` Jonathan Frederickson
2019-10-26  1:19     ` Jonathan Frederickson
2019-10-26 10:00   ` Pierre Neidhardt
2019-10-27  3:29     ` Bengt Richter
2019-10-27  8:49       ` Pierre Neidhardt
2019-10-27 13:33     ` Konrad Hinsen
2019-10-27 13:53       ` Jelle Licht
2019-11-03 14:24   ` Ludovic Courtès
2019-11-03 16:49     ` Jonathan Frederickson
2019-11-04 10:12       ` Pierre Neidhardt
2019-11-04 14:33       ` Ludovic Courtès
2019-11-04 10:10     ` Pierre Neidhardt
2019-11-05 22:18       ` Carlo Zancanaro
2019-11-06  8:32         ` Pierre Neidhardt
2019-11-06 17:37           ` Ludovic Courtès
2019-11-07 12:42             ` Pierre Neidhardt
2019-10-26 18:32 ` Alex Griffin
2019-10-26 19:38   ` Pierre Neidhardt
  -- strict thread matches above, loose matches on Subject: below --
2019-11-02 18:51 Tanguy Le Carrour
2019-11-02 19:21 ` Pierre Neidhardt

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=20191027085652.75yygzkf3vttcpjz@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).