all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: L  p R n  d n    <guix@lprndn.info>
To: guix-devel@gnu.org
Subject: Re: Brain storming cool Guix features
Date: Mon, 07 Jan 2019 17:48:39 +0100	[thread overview]
Message-ID: <cucpnt82z2w.fsf@lprndn.info> (raw)
In-Reply-To: <87bm4wwrku.fsf@dismail.de> (Joshua Branson's message of "Fri, 04 Jan 2019 07:11:13 -0500")


Hellohello,

Joshua Branson <jbranso@dismail.de> writes:

> I had some cool ideas/features for things that GuixSD could potentially
> add, and I wanted to share.  Are any of these possible?
>
> #+BEGIN_SRC scheme
> (operating system
>   (keymap  "dvorak")
>   ...)
> #+END_SRC
>
>
> The above would make the bootloader, console, X, and wayland all use the
> dvorak layout.  That would be a nice feature!  I currently use "dvorak",
> and it's slightly annoying that grub uses qwerty.  :(
>
> #+BEGIN_SRC
> (user-account
>    (name "joshua")
>    (default-font "font-hack"))
> #+END_SRC
>
>
> The above would set a default font for the user joshua.
>
>
> How about a hook that stores the user's profile of packages in a
> manifest file after every package transaction (upgrade or downgrade)?
>
> #+BEGIN_SRC
> (user-account
>         (name "joshua")
>         (updates-in-manifest #t)
>         (manifest-file "/etc/manifest.scm"))
> #+END_SRC

The ability to deal with user profiles in the configure file would be
awesome. Is it already possible to define a "default" manifest for a
user? If not, could be cool too.  

>
> How about automatic updates?  Since a guixSD user can always downgrade
> to the previous version, it would be nice if it would automatically
> update my user profile, root profile and reconfigure say once a week.
>
> #+BEGIN_SRC scheme
> (operating system
>   (auto-upgrade #t)
>   (auto-upgrade-interval 'once-a-week)
>   ...)
> #+END_SRC

As said by Ricardo, currently a cron job might just be enough. In the
long term, a tool to manage updating (pause, schedule, configure stuff)
could be useful.

> --
> Joshua Branson
> Sent from Emacs and Gnus


If I can add, I thought about something.

- Currently, I think the only way for a GuixSD installation to break is
  if something goes wrong with the bootloader. Might be nice to have a
  tool (in the install image I suppose) to recover the bootloader.
  Maybe 'guix system init' can deal with that king of cases for now, I
  don't know, but a dedicated command might be able to use the original
  store, restore previous generations etc.

Bye,

Lprndn

  parent reply	other threads:[~2019-01-07 15:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 12:11 Brain storming cool Guix features Joshua Branson
2019-01-04 16:01 ` Ricardo Wurmus
2019-01-05 13:59   ` Joshua Branson
2019-01-05 17:06     ` Ricardo Wurmus
2019-01-13 20:18   ` Joshua Branson
2019-01-13 21:36     ` bug#25453: Keyboard layout configuration Ludovic Courtès
2019-01-13 22:49       ` nee
2019-01-15 22:21         ` bug#25453: " Ludovic Courtès
2019-01-15 22:21         ` Ludovic Courtès
2019-03-12 19:34           ` bug#25453: " Taylan Kammer
2019-03-15 18:19             ` nee
2019-03-21 22:23               ` Taylan Kammer
2019-03-12 19:34           ` Taylan Kammer
2019-03-20 23:07           ` Ludovic Courtès
2019-03-20 23:07           ` Ludovic Courtès
2019-01-16 13:10         ` Ludovic Courtès
2019-01-16 13:10         ` Ludovic Courtès
2019-01-13 22:49       ` bug#25453: " nee
2019-01-04 16:10 ` Brain storming cool Guix features Pierre Neidhardt
2019-01-04 16:14   ` John Soo
2019-01-04 16:58 ` znavko
2019-01-06 13:44   ` Amirouche Boubekki
2019-01-06 16:33     ` swedebugia
2019-01-06 20:04       ` Amirouche Boubekki
2019-01-07 16:48 ` L p R n d n [this message]
2019-01-07 18:16   ` Joshua Branson
2019-01-11 22:32   ` GRUB fallback mechanism [was Re: Brain storming cool Guix features] Leo Famulari
2019-01-12 12:59     ` swedebugia
2019-01-12 15:58       ` Ricardo Wurmus
2019-01-13 20:58         ` Ludovic Courtès
2019-01-14 14:15           ` L p R n d n

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cucpnt82z2w.fsf@lprndn.info \
    --to=guix@lprndn.info \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.