From: gfp <gfp@posteo.at>
To: Ian Eure <ian@retrospec.tv>
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, 9 Dec 2024 19:25:58 +0000 [thread overview]
Message-ID: <e1ff100d-9ee2-490c-8acf-76e8ddf3cb66@posteo.at> (raw)
In-Reply-To: <878qsoaich.fsf@retrospec.tv>
[-- Attachment #1.1.1: Type: text/plain, Size: 2282 bytes --]
Hi,
1.
Approx. 2 years ago some Guixers proposed to create profiles in order to
have not too many packages in the main profile, which makes it easier to
update the profile. If during updating the profile one package creates
trouble, the whole updating process stops. I had those trouble several
times.
2.
If I put all packages in the main profile, I would have approx. 30
packages more and altogether approx. 120 packages at the moment, and
there will be more in future.
I don´t use "guix home"
3.
May be those Guixers have special needs and it works easier for them.
Of course, those Guixers know what they are doing unlike me.
4.
If I had all packages in my main profile, would it be possible to update
only some packages?
e.g. icecat and others quite regularly are updated, so it would be good
to update them more often.
thanks for your help
Gottfried
Am 09.12.24 um 18:15 schrieb Ian Eure:
> 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
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2451 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
next prev parent reply other threads:[~2024-12-09 19:26 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
2024-12-09 19:25 ` gfp [this message]
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=e1ff100d-9ee2-490c-8acf-76e8ddf3cb66@posteo.at \
--to=gfp@posteo.at \
--cc=help-guix@gnu.org \
--cc=ian@retrospec.tv \
--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).