unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: 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: Fri, 06 Jan 2023 16:45:25 +0100	[thread overview]
Message-ID: <87fscnis4q.fsf@gmail.com> (raw)
In-Reply-To: <00645283-6540-ea05-aba2-8997d32b16c1@posteo.de>

Hi,

On Wed, 28 Dec 2022 at 15:09, Gottfried <gottfried@posteo.de> wrote:

> Which commands can I use to enter and close my new profile?

To enter, you just need to ’source path/to/some-profile/etc/profile’.

However, you cannot “deactivacte“; unset the environment variables and
restore the previous ones.  Maybe, the easiest is:

   bash
   source path/to/some-profile/etc/profile
   …do some stuff…
   exit

Instead, you can run

    guix shell -p path/to/some-profile/etc/profile
    …do some stuff…
    exit

which does the same thing as above.


> ...and also at start up that I can choose which profile to open?

What do you mean by “choose”?


> guix package --profile=/home/gfp/projects/musescore-3.6.2.guix-profile
>
> and beforehand I created the directory "projects" and
> "Musescore-3.6.2" in the directory "projects"
> in my /home/gfp/ directory
> (I did that because it said: "
> file or directory was not found"
>
> but it didn't work.
> "warning: nothing to do" was the answer.
>
> Where was my mistake?

It is missing the option -i (or -m).  For instance,

    guix package -i musescore -p projects/musescore-3.6.2.guix-profile


Cheers,
simon



  reply	other threads:[~2023-01-06 16:31 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 [this message]
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
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=87fscnis4q.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gottfried@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=koszko@koszko.org \
    --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).