unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: gfp <gfp@posteo.at>
Cc: Rutherther <rutherther@ditigal.xyz>,
	 Steve George <steve@futurile.net>,
	help-guix@gnu.org
Subject: Re: how can I open files through packages installed in different profiles
Date: Mon, 09 Dec 2024 09:15:10 -0800	[thread overview]
Message-ID: <878qsoaich.fsf@retrospec.tv> (raw)
In-Reply-To: <2f722a8f-ec65-4168-8f54-6e425524a336@posteo.at> (gfp@posteo.at's message of "Sun, 8 Dec 2024 19:44:00 +0000")

Hi gfp,

gfp <gfp@posteo.at> writes:

> I have got 17 Profiles in:
> /home/gfp/Projekte/Calibre
> 		  /Emacs
> 		  /Libreoffice
> 		  etc.
>
>  Would that mean to sorce all 17 profiles in one go? or only two 
>  at a time?

I agree with Steve: you shouldn’t use profiles like this.  By 
activating all these profiles at once, you’re effectively creating 
a single profile with the combined packages of all 17.  But since 
this is done in an ad-hoc way, outside Guix, it’s missing 
functionality, such as telling you about conflicts, building the 
XDG MIME database, font cache, etc.  This is very likely going to 
cause further bugs and problems.

If you put the software you regularly use into your main profile, 
the system works better and your problem goes away without needing 
to mess with shell startup.

Engineering is all about making tradeoffs.  With the downsides 
you’ve noted, and the complexity of managing it, I’d expect there 
to be a very strong and specific upside from such a system which 
can’t be replicated with a one-profile setup.  I may have missed 
it, but I don’t see such a rationale here.

I strongly urge you to reconsider your approach.

  -- Ian


  parent reply	other threads:[~2024-12-09 17:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 19:29 how can I open files through packages installed in different profiles gfp
2024-11-18 14:58 ` Steve George
2024-12-07 13:08   ` gfp
2024-12-07 14:02     ` Rutherther
2024-12-07 15:28       ` gfp
2024-12-07 20:09         ` Rutherther
2024-12-08 19:44           ` gfp
2024-12-08 21:19             ` Rutherther
2024-12-09 19:15               ` gfp
2024-12-09 17:15             ` Ian Eure [this message]
2024-12-09 19:25               ` gfp
2024-12-09 20:03                 ` Ian Eure
2024-12-10 12:36                 ` Andreas Enge

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=878qsoaich.fsf@retrospec.tv \
    --to=ian@retrospec.tv \
    --cc=gfp@posteo.at \
    --cc=help-guix@gnu.org \
    --cc=rutherther@ditigal.xyz \
    --cc=steve@futurile.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).