From: "Todor Kondić" <tk.code@protonmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>,
"guix-blog@gnu.org" <guix-blog@gnu.org>
Subject: Re: [Blog/Cookbook?] On multiple Guix profiles and manifests
Date: Mon, 07 Oct 2019 16:17:10 +0000 [thread overview]
Message-ID: <Ur5kgJ2hQRiL55jwRFGB3Xpz3PG_3TtSvwkVURhMUlC2YcUMU6aHUC3KQnnk6FGk_H9wFhb30lHOudEjj3zxSH6uH1FefUCjpU_BIeP1cv8=@protonmail.com> (raw)
In-Reply-To: <m1v9t0woqn.fsf@khs-macbook.home>
On Monday, 7 October 2019 17:37, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
> Pierre Neidhardt mail@ambrevar.xyz writes:
>
> > Konrad Hinsen konrad.hinsen@fastmail.net writes:
> >
> > > Sounds good in principle. I just wonder how many authors (and thus
> > > different preferences and use cases) it takes to make this really
> > > useful. I note for example that my own use of profiles is rather
> > > different from yours: I have per-project profiles for long-term projects
> > > whose software I don't want to update regularly to avoid breaking stuff.
> >
> > Hmmm, this sounds like what I do too! :)
>
> The main difference is that I don't have all my profiles activated
> in normal use, only my main profile plus one project profile. Different
> project profiles can contain different versions of the same software,
> so activating them together is not a good idea.
>
> What got me started with this strategy was the need to use
> Python 2 and Python 3 in different projects. But then it turned out to
> be useful for other software as well.
Persistent environments anyone? :)
> > Anyways, I'm all for discussing multiple strategies, the more the better!
>
> Sounds like a good plan!
>
> Cheers,
> Konrad
next prev parent reply other threads:[~2019-10-07 16:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 10:55 [Blog/Cookbook?] On multiple Guix profiles and manifests Pierre Neidhardt
2019-10-07 9:56 ` Todor Kondić
2019-10-07 15:17 ` Pierre Neidhardt
2019-10-07 14:05 ` Konrad Hinsen
2019-10-07 15:25 ` Pierre Neidhardt
2019-10-07 15:37 ` Konrad Hinsen
2019-10-07 16:17 ` Todor Kondić [this message]
2019-10-11 8:23 ` Ludovic Courtès
2019-10-11 15:16 ` Pierre Neidhardt
2019-10-11 16:51 ` Ricardo Wurmus
2019-10-12 8:34 ` Pierre Neidhardt
2019-10-12 23:08 ` Ludovic Courtès
2019-10-13 10:27 ` Pierre Neidhardt
2019-10-14 10:35 ` Pierre Neidhardt
2019-10-14 13:30 ` Ludovic Courtès
2019-10-14 4:38 ` Chris Marusich
2019-10-14 7:27 ` Pierre Neidhardt
2019-10-14 11:26 ` Konrad Hinsen
2019-10-14 11:49 ` Pierre Neidhardt
2019-10-14 14:53 ` Chris Marusich
2019-10-14 15:01 ` Chris Marusich
2019-10-14 15:39 ` 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='Ur5kgJ2hQRiL55jwRFGB3Xpz3PG_3TtSvwkVURhMUlC2YcUMU6aHUC3KQnnk6FGk_H9wFhb30lHOudEjj3zxSH6uH1FefUCjpU_BIeP1cv8=@protonmail.com' \
--to=tk.code@protonmail.com \
--cc=guix-blog@gnu.org \
--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).