unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Collect guix profiles in single directory.
Date: Mon, 6 Jan 2020 19:55:35 +0100	[thread overview]
Message-ID: <CAJ3okZ0SNnQ5ai7Ju6PV3ePXDKM2ArBA1YZM57ZmDHeFTKXTdA@mail.gmail.com> (raw)
In-Reply-To: <eabe0cccdb377b1c573df88715d6aebf7bf7f80c.camel@student.tugraz.at>

Hi,

On Mon, 23 Dec 2019 at 12:00, Leo Prikler <leo.prikler@student.tugraz.at> wrote:


> This is a proposal to change the current approach.  Instead of
> splitting Guix config in a way that tries to conform to XDG, but does
> not really, I propose to use a single directory ~/.guix for all
> configuration.

Maybe I misread something but instead I would prefer to move
~/.guix-profile under XDG standard, i.e.,
 - ~/.config/guix/current (or whatever name remembering it is used by
"guix pull")
 - ~/.config/guix/default (or 'profile') playing the role of ~/.guix-profile

Other profiles could be added (by default) under
~/.config/guix/<name-it>. Well, instead of ~/.guix/ I would prefer to
have ~/.config/guix/.

However, I agree that it could be a first step to have Channels
manager (as it was discussed some weeks ago) or Profile manager (also
discussed some weeks ago).


(Personally, I prefer having my profile living in the folders of my
projects, but that another story. ;-)

All the best,
simon

  reply	other threads:[~2020-01-06 18:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 10:59 Collect guix profiles in single directory Leo Prikler
2020-01-06 18:55 ` zimoun [this message]
2020-01-06 20:07   ` Alex Griffin
2020-01-06 22:52     ` zimoun
2020-01-07 13:02   ` Leo Prikler
2020-01-06 19:41 ` Pierre Neidhardt
2020-01-08 11:25 ` Ludovic Courtès
2020-01-08 13:48   ` Leo Prikler
2020-01-08 14:16     ` Pierre Neidhardt
2020-01-30 19:28       ` Pierre Neidhardt
2020-01-30 20:08         ` [ SPAM? ] " Leo Prikler
2020-01-31  7:59           ` Pierre Neidhardt
2020-01-31  8:46             ` zimoun
2020-01-31  9:29               ` Leo Prikler
2020-01-31 12:04                 ` Pierre Neidhardt
2020-01-31 12:56                   ` Leo Prikler
2020-01-31 13:36                     ` Pierre Neidhardt
2020-01-31 11:06               ` [ SPAM? ] " Pierre Neidhardt
2020-01-31  9:18             ` Leo Prikler
2020-01-31 13:33               ` Pierre Neidhardt
2020-01-31 14:34                 ` Leo Prikler
2020-01-31 15:17                   ` Pierre Neidhardt
2020-01-31 15:38                     ` Leo Prikler
2020-01-31 15:52                       ` Pierre Neidhardt
2020-01-08 11:44 ` Raghav Gururajan

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=CAJ3okZ0SNnQ5ai7Ju6PV3ePXDKM2ArBA1YZM57ZmDHeFTKXTdA@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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 public inbox

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

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