unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Kyle Andrews <kyle@posteo.net>
Cc: Gottfried <gottfried@posteo.de>, Csepp <raingloom@riseup.net>,
	Wojtek Kosior <koszko@koszko.org>,
	help-guix@gnu.org
Subject: Re: attempt to create a profile
Date: Mon, 06 Feb 2023 18:21:48 +0100	[thread overview]
Message-ID: <87357ik8ur.fsf@gmail.com> (raw)
In-Reply-To: <877cwx6kdh.fsf@posteo.net>

Hi,

On sam., 04 févr. 2023 at 23:36, Kyle Andrews <kyle@posteo.net> wrote:

>>     guix shell -p path/to/some-profile/etc/profile

This command is incorrect and it should read instead,

    guix shell -p path/to/some-profile

but anyway, it was the idea. :-)


> Is it possible to use guix shell to activate multiple existing profiles
> in a particular order to explicitly test for incompatibilities when
> combining profiles?

Well, I am not aware about a way to compose some profiles with “guix
shell”.  Indeed, it should be possible, IMHO.  But I have not checked if
it is technically possible.  Maybe it is already. :-)


> In conclusion, I'm a bit surprised that activating multiple profiles at
> once is so easily found and recommended in the cookbook. It seems to me
> like there are many underemphasized gotchas with respect to
> reproducibility and usability which come from it and as far as I can
> tell, the main developers of Guix do not use it that way. If it is going
> to be recommended as atleast a possibility for advanced users, then it
> would be nice to be able to formally test that usage through ~guix shell~.

I am using multiple profiles and I barely hit collisions.  Given one
specific revision of Guix, collisions should not be possible – it means
something is wrong somewhere with package definition; although, maybe it
is impossible to avoid some collisions with large number of packages,
anyway. :-)

Most of the time, collisions happen when the profile are coming from
different revision of Guix.  And try to combine several profiles from
different revision is, IMHO, some source of troubles impossible to
solve.

That’s said, yes I would also like being able to combine several
profiles and also extend the result.


Cheers,
simon


  reply	other threads:[~2023-02-06 18:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 15:09 attempt to create a profile Gottfried
2023-01-06 15:45 ` Simon Tournier
2023-01-09 15:59   ` Gottfried
2023-01-11 21:27     ` Simon Tournier
2023-01-11 16:55   ` Gottfried
2023-02-04 23:36   ` Kyle Andrews
2023-02-06 17:21     ` Simon Tournier [this message]
2023-02-07 10:06       ` Gottfried
2023-02-07 11:03         ` zimoun
2023-02-07 13:33           ` Gottfried
2023-02-08  1:25             ` Csepp
2023-02-08  9:58               ` Simon Tournier
2023-02-09 14:21                 ` Gottfried
2023-02-09 14:44               ` Gottfried
2023-02-09 19:20                 ` Csepp
2023-02-11 16:20                   ` Gottfried
2023-02-11 17:30                     ` Csepp
2023-02-12 12:15                       ` Gottfried
2023-02-14  4:45       ` Kyle Andrews
2023-02-14  5:40         ` 宋文武
2023-02-14  6:00           ` Kyle Andrews
2023-02-14 11:04             ` Simon Tournier
     [not found] <mailman.95.1673024475.17576.help-guix@gnu.org>
2023-01-08  9:21 ` Gottfried
2023-01-08 10:52   ` Csepp

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=87357ik8ur.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gottfried@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=koszko@koszko.org \
    --cc=kyle@posteo.net \
    --cc=raingloom@riseup.net \
    /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).