unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: raingloom <raingloom@riseup.net>
To: "Cássio Tavares" <cassio.ufg@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix pull; guix package -u; sudo guix system reconfigure /etc/config.scm
Date: Thu, 28 Apr 2022 01:18:02 +0200	[thread overview]
Message-ID: <20220428011758.5f27265e@riseup.net> (raw)
In-Reply-To: <CAJTCCxOev=W0NV0ywrrmDfSXdwngth24+-qPD55QmPnhk6QDiQ@mail.gmail.com>

(reply is at bottom)

On Wed, 27 Apr 2022 21:29:54 +0000
Cássio Tavares <cassio.ufg@gmail.com> wrote:

> On Fri, Apr 8, 2022 at 2:40 AM raingloom <raingloom@riseup.net> wrote:
> 
> > On Thu,  7 Apr 2022 20:40:07 +0000
> > Gottfried <gottfried@posteo.de> wrote:
> >  
> > > As I understood I should do a "guix pull" every week.
> > >
> > > But what is with "guix package -u"
> > > When I did it two days ago it took 6 hours. I couldn't swich off
> > > my laptop. So I can do it only when having a lot of time.
> > > Normally it took approx. 30 min
> > > If I don't need always the latest version, I can do it once a
> > > month or once in two month
> > > Is that okay?  
> >
> > I'd recommend just skipping the few packages that take too long to
> > build.
> > Before upgrading, run guix package --upgrade --dry-run, and see what
> > would be downloaded and what would be built locally.
> > If there is something too large there, use the --do-not-upgrade
> > flag. It can be given multiple times.
> >
> > Also sometimes the reason something is built locally is because its
> > derivation failed on the substitute server, and I think it kinda
> > sucks that the user doesn't get warned about that, because building
> > half of Firefox just to see it fail with the same error message as
> > it did on the server is a huge waste of electricity, and also my
> > time. 
> > > Do I have to do a "sudo guix system reconfigure /etc/config.scm"
> > > always after the "guix package -u"?
> > > Can I do it every month or every second month? when I don't need
> > > the latest version of packages?
> > >
> > > Gottfried
> > >  
> >
> > I solve the latter by having a very lean system profile, only the
> > bare essentials are installed for the whole system, things like the
> > window manager are only in my user profile.
> >
> >  
> If your window manager is only in your profile, then it won't be
> available for the display manager's login. Is there a workaround for
> that? Cássio
> -----
> Faculdade de Letras - UFG
> *“*
> *Ou a gente se Raôni, ou a gente se Sting**”*
> 
> 

Possibly. This might be a good starting point:
https://wiki.archlinux.org/title/Display_manager#Session_configuration
That requires a modification to /usr, which seems like a bad idea.
Maybe someone else can figure out the details, I don't have time to do
a deep dive right now.


Sorry for editing your reply, but as the old joke goes:

Because it's messing up the reading order.
>Why?
>>Please stop top-posting.


  reply	other threads:[~2022-04-27 23:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 20:40 guix pull; guix package -u; sudo guix system reconfigure /etc/config.scm Gottfried
2022-04-08  2:38 ` raingloom
2022-04-27 21:29   ` Cássio Tavares
2022-04-27 23:18     ` raingloom [this message]
2022-04-08  6:50 ` David Lecompte via
2022-04-28 14:15 ` EuAndreh
  -- strict thread matches above, loose matches on Subject: below --
2022-04-10 10:01 Gottfried
2022-04-12  0:42 ` raingloom

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=20220428011758.5f27265e@riseup.net \
    --to=raingloom@riseup.net \
    --cc=cassio.ufg@gmail.com \
    --cc=help-guix@gnu.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).