unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <rg@raghavgururajan.name>
To: guix-devel@gnu.org
Cc: "Leo Prikler" <leo.prikler@student.tugraz.at>,
	"Nicolò Balzarotti" <anothersms@gmail.com>
Subject: Re: An idea regarding Guix Profiles
Date: Thu, 28 Jan 2021 16:43:10 -0500	[thread overview]
Message-ID: <7b654b71-59f1-91f5-0641-b0d6e78755bc@raghavgururajan.name> (raw)
In-Reply-To: <9b4c89b6-761a-d7a1-c7d9-a5a191ef4eb1@raghavgururajan.name>

Hello Guix!

>> I just had this crazy idea.
>>
>> Currently, we can create multiple profiles at user-level. What if we 
>> could bring the 'guix profiles' concept to system-level?
>>
>> At user-level, user can choose which profile to work on. Like that it 
>> would be cool to select which profile to boot.
>>
>> Thoughts?
> 
> For clarification, I meant these multiple system-profiles to be 
> different from generations.
> 
> Currently, there can be only one system-profile, under which there can 
> be many generations. In my idea, each multiple system-profile, will have 
> their own generations.
> 
> For Example,
> 
> ```
> System 1 (Desktop installation for generic/casual use):
>      Generation 1
>      Generation 2
>      ...
> 
> System 2 (Minimal installation for development use):
>      Generation 1
>      Generation 2
>      ...
> 
> System 3 (Base installation for home-server use):
>      Generation 1
>      Generation 2
>      ...
> ```
> 
> If a user wants to casually watch multimedia or browse the web or edit 
> some documents, the user can choose the system-profile 'System 1'. There 
> will be desktop-environment and system-services for generic/casual use.
> 
> If a user wants to do development work, the user can choose the 
> system-profile 'System 2'. There will be minimal window-managers and 
> system-services for development use.
> 
> If a user is going to travel and want to run the machine as home-server, 
> so that it can be accessed/used remotely, the user can choose the 
> system-profile 'System 3'. There will be base packages and specific 
> system-services like SSH, NFS etc.
> 
> Another Example,
> 
> ```
> System 1 (GNU/Linux-Libre):
>      Generation 1
>      Generation 2
>      ...
> 
> System 2 (GNU/Hurd):
>      Generation 1
>      Generation 2
>      ...
> 
> System 3 (GNU/HyperbolaBSD):
>      Generation 1
>      Generation 2
>      ...
> ```

But if these profiles are gonna defined in same config.scm, then the 
generations will be shared.

  ```
Generation Current:
  System Profile 1 (Desktop installation for generic/casual use)
  System Profile 2 (Minimal installation for development use)
  System Profile 3 (Base installation for home-server use)

Generation 6:
  System Profile 1 (Desktop installation for generic/casual use)
  System Profile 2 (Minimal installation for development use)
  System Profile 3 (Base installation for home-server use)

Generation 5:
  System Profile 1 (Desktop installation for generic/casual use)
  System Profile 2 (Minimal installation for development use)
  System Profile 3 (Base installation for home-server use)

[...]
  ```

OR

  ```
Generation Current:
  System Profile 1 (GNU/Linux)
  System Profile 2 (GNU/Hurd)
  System Profile 3 (GNU/BSD)

Generation 6:
  System Profile 1 (GNU/Linux)
  System Profile 2 (GNU/Hurd)
  System Profile 3 (GNU/BSD)

Generation 5:
  System Profile 1 (GNU/Linux)
  System Profile 2 (GNU/Hurd)
  System Profile 3 (GNU/BSD)

[...]
  ```

Regards,
RG.


  reply	other threads:[~2021-01-28 21:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  4:05 An idea regarding Guix Profiles Raghav Gururajan
2021-01-28  7:54 ` Maxime Devos
2021-01-28  8:23 ` Pierre Neidhardt
2021-01-28 10:35 ` Nicolò Balzarotti
2021-01-28 21:18 ` Raghav Gururajan
2021-01-28 21:43   ` Raghav Gururajan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-28  8:11 Leo Prikler
2021-01-28 10:17 ` Leo Prikler

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=7b654b71-59f1-91f5-0641-b0d6e78755bc@raghavgururajan.name \
    --to=rg@raghavgururajan.name \
    --cc=anothersms@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).