unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Raghav Gururajan" <raghavgururajan@disroot.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Leo Prikler" <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org
Subject: Re: Collect guix profiles in single directory.
Date: Wed, 08 Jan 2020 11:44:24 +0000	[thread overview]
Message-ID: <13f0e30551c27859ef5ee7333a4657e3@disroot.org> (raw)
In-Reply-To: <87blrefavb.fsf@gnu.org>

Hello Ludo!

> To me, the most important aspect of your proposal is having all profiles
> in one place (Konrad proposed something similar recently, well, “last
> year.” :-))
> 
> Like I wrote then, ‘guix package --list-profiles’ was an attempt at
> making it easier to locate profiles, even if they’re not in the same
> directory, so that you can easily operate on them. What Konrad noted is
> that this returns all the profiles, including
> ~/.config/guix/current-kind of profiles, which may be inconvenient.
> 
> I’m generally wary of enforcing arbitrary conventions, such as a
> specific directory to store all profiles, but at the same time I agree
> that this can be convenient, so I’m a bit split!
> 
> Also, such a change would need a transition plan: what does ‘-p’ become, etc.
> 
> Thoughts?

I just subscribed to guix-devel and happen to see this email.

I had similar thoughts before, that is putting all profiles under single directory.

I was conceptualizing this:

The way we track or mark a particular generations as current generations, I think we can apply same concept to profiles. For example, instead of having 'default-profile' in one directory and others in 'extra-profile' directories; all profiles will be put under one directory. There will be first initial profile '0' created automatically for each user; just like how system generation '0' is created. Then, a user can create as many profiles as they want. It will be tracked as 1, 2, 3 and so on. But here we can a tag something like 'default'. similar to 'current' tag for generations. User can change which profile to be default through `--change-default'; just like '--switch-generation'.

      parent reply	other threads:[~2020-01-08 11:44 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
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 [this message]

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=13f0e30551c27859ef5ee7333a4657e3@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=ludo@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 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).