From: Csepp <raingloom@riseup.net>
To: Wojtek Kosior <koszko@koszko.org>
Cc: Gottfried <gottfried@posteo.de>, Csepp <raingloom@riseup.net>,
help-guix@gnu.org
Subject: Re: installing of two versions of package Musescore
Date: Tue, 27 Dec 2022 12:30:34 +0100 [thread overview]
Message-ID: <871qolf5ck.fsf@riseup.net> (raw)
In-Reply-To: <20221226193300.296fae7e.koszko@koszko.org>
Wojtek Kosior <koszko@koszko.org> writes:
> [[PGP Signed Part:Undecided]]
> Hi Gottfried,
>
>> 3. I want to have "Musescore3.6.2" as the name of this profile, so that
>> I quickly now what is in there. Is that possible? If not how this
>> profile is specified to see the difference to my main profile?
>>
>> 4. what should I write in "path/to/profile"
>> because AFAIU the profile will be in
>> /etc/
>>
>> like this?:
>>
>> profileMusescore3.6.2
>>
>> /etc/profileMusescore3.6.2
>>
>> "guix package --profileMusescore3.6.2=/etc/profileMusescore3.6.2"
>
> Good news for you — the profile does not need to reside under `/etc/`.
> In fact, it would be abnormal to have a non-root user's profile there
> since `/etc/` is usually only writeable by root.
>
> User's profiles usually live somewhere under the user's HOME directory.
> I'd personally choose a path like `~/.guix-profiles/musescore-3.6.2`.
> Someone else would perhaps use `~/.config/guix/Musescore3.6.2`. Just
> pick what you like the most.
I usually put them in project specific directories, like so:
"$HOME/Graphics/.guix-profile"
"$HOME/Projects/Advent of Code/2022/.guix-profile"
and so on...
I find that it's much easier to use than if they were centralized under
one directory, because this way they are close to the project they
correspond to.
Also, a useful command to know:
guix package --list-profiles
prev parent reply other threads:[~2022-12-27 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 8:23 installing of two versions of package Musescore Gottfried
2022-12-19 13:55 ` Csepp
2022-12-19 14:19 ` Gottfried
2022-12-20 17:02 ` Csepp
2022-12-21 13:17 ` Gottfried
2022-12-21 18:06 ` Csepp
2022-12-22 13:21 ` Gottfried
2022-12-22 14:47 ` Csepp
2022-12-21 18:53 ` Wojtek Kosior via
2022-12-24 14:08 ` Gottfried
2022-12-26 18:33 ` Wojtek Kosior via
2022-12-27 11:30 ` Csepp [this message]
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=871qolf5ck.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=koszko@koszko.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).