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 12:03:41 -0800	[thread overview]
Message-ID: <87ldwo8vz6.fsf@retrospec.tv> (raw)
In-Reply-To: <e1ff100d-9ee2-490c-8acf-76e8ddf3cb66@posteo.at> (gfp@posteo.at's message of "Mon, 9 Dec 2024 19:25:58 +0000")

gfp <gfp@posteo.at> writes:

> 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.
>

What kinds of problems?

Guix is a transactional package manager, so one failure must halt 
the operation it occurred within.  This is one of the tradeoffs of 
the Guix system, and it certainly can lead to some annoying 
situations.  If it’s a major problem for you, you might consider 
another distro, or using Guix on a foreign distro, where you let 
the other package management system handle some of the software.

> 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.
>

That seems fine.

> 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.
>

One of the best things about Guix is how you can tailor it to your 
tastes!  I would definitely recommend experimenting a bit to find 
something that works for you.


> 4.
> If I had all packages in my main profile, would it be possible 
> to
> update only some packages?
>

I believe `guix package -u package-name-or-regexp' will do what 
you want, but can’t test it.


> e.g. icecat and others quite regularly are updated, so it would 
> be
> good to update them more often.
>

Note also that by not updating packages in profiles, you’re 
increasing the number of vulnerabilites you’re subject to (and 
making it harder to update to fix them).  For example, if an 
OpenSSL vuln is patched, and two of your profiles have packages 
which need the library, they’ll remain vulnerable until you 
upgrade within those profiles.

  -- Ian


  reply	other threads:[~2024-12-09 20:04 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
2024-12-09 20:03                 ` Ian Eure [this message]
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=87ldwo8vz6.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).