all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrew Tropin <andrew@trop.in>
To: Xinglu Chen <public@yoctocell.xyz>, Oleg Pykhalov <go.wigust@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Merging wip-guix-home to master
Date: Thu, 30 Sep 2021 09:11:46 +0300	[thread overview]
Message-ID: <87o88aoan1.fsf@trop.in> (raw)
In-Reply-To: <87y27f1uh2.fsf@yoctocell.xyz>

[-- Attachment #1: Type: text/plain, Size: 3677 bytes --]

On 2021-09-29 13:39, Xinglu Chen wrote:

> On Tue, Sep 28 2021, Andrew Tropin wrote:
>
>> On 2021-09-24 15:38, Xinglu Chen wrote:
>>
>>> On Thu, Sep 23 2021, Andrew Tropin wrote:
>>>
>>>> The core part of Guix Home project has been moved from rde
>>>> repository[fn:1] to wip-guix-home branch of guix repository.
>>>>
>>>> I'm about a week on wip-guix-home branch completely and Guix Home works
>>>> fine.  There are no any major issues on rde-devel and guix-devel mailing
>>>> lists and it seems that branch is ready to be merged.
>>>>
>>>> My guix describe looks like:
>>>> --8<---------------cut here---------------start------------->8---
>>>> Generation 114	Sep 17 2021 13:33:55	(current)
>>>>   rde 31f8003
>>>>     repository URL: https://git.sr.ht/~abcdw/rde
>>>>     branch: without-guix-home
>>>>     commit: 31f800353a781cef25fc80c05ad824a068a049c8
>>>>   guix a2324d8
>>>>     repository URL: https://git.savannah.gnu.org/git/guix.git
>>>>     branch: wip-guix-home
>>>>     commit: a2324d8b56eabf8117bca220a507cc791edffd2e
>>>> --8<---------------cut here---------------end--------------->8---
>>>>
>>>>
>>>> There is a discussion[fn:2] on moving home services to (gnu services
>>>> ...)  modules, which is likely to happen, but it's possible to do the
>>>> migration relatively painless by re-exporting necessary symbols in
>>>> (gnu home-services ...) at first and removing them completely later.
>>>>
>>>> Another important part of the work related to Guix Home project is
>>>> covering related modules and cli with tests, but it can be done in
>>>> parallel and is not a blocker for merging.
>>>
>>> I noticed that the ‘guix home import’ subcommand is included, but I
>>> think it needs more thought and feedback from people before it makes its
>>> way into ‘master’; it also seems to lack documentation.
>>>
>>> I just realized that it generates the following service declaration
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> (service
>>>  home-bash-service-type
>>>  (home-bash-configuration
>>>   (bashrc
>>>    (list (slurp-file-gexp
>>>           (local-file "/home/yoctocell/.bashrc"))))))
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> but when running ‘guix home reconfigure’, the ~/.bashrc file will be
>>> moved, so when running ‘guix home reconfigure’ for the second time, it
>>> would read the ~/.bashrc which is itself a symlink to a file the store.
>>> ‘guix home import’ clearly isn’t in a usable state as of right now…
>>
>> Yep, I remember that it is not documented.  I think it's ok for
>> generating a simple sample configuration,

It was two independent sentences.

>
> I disagree, I think it’s OK for things like (guix git), which are mainly
> used by developers, to not be documented in the manual.  Ideally, the
> all the modules would be documented.  :-)
>
> However, ‘guix home import’ will be used by developers and regular
> users, and documenting the command should be a requirement.
>
>> but I agree that it's not yet complete, if you wish I'll disable it in
>> cli.
>
> I have sent a few patches to fix it and document it[1], so it should
> probably left as-is for now.
>
>> Just an idea for the future: it's probably better to copy .bashrc to the
>> current directory and do (local-file "./bashrc").
>
> This wouldn’t work if the user doesn’t have write-access to the current
> directory, nor if the current directory is $HOME.  I think it’s better
> for the user to specify the directory themselves.
>
> [1]: <https://issues.guix.gnu.org/50873>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2021-09-30  6:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  9:53 Merging wip-guix-home to master Andrew Tropin
2021-09-23 14:36 ` [bug#50753] " Oleg Pykhalov
2021-09-24  7:10   ` Andrew Tropin
2021-09-27 14:38     ` bug#50753: " Oleg Pykhalov
2021-09-28  7:10       ` [bug#50753] " Andrew Tropin
2021-09-28  7:45         ` zimoun
2021-09-28  9:41           ` Andrew Tropin
2021-09-28 10:13           ` Ludovic Courtès
2021-09-23 15:27 ` Katherine Cox-Buday
2021-09-24  7:12   ` Andrew Tropin
2021-09-23 20:45 ` Ludovic Courtès
2021-09-24  7:43   ` Andrew Tropin
2021-09-24 13:38 ` Xinglu Chen
2021-09-28 10:14   ` Andrew Tropin
2021-09-29 11:39     ` Xinglu Chen
2021-09-29 14:15       ` Katherine Cox-Buday
2021-09-29 15:02         ` Xinglu Chen
2021-09-30  6:11       ` Andrew Tropin [this message]
2021-09-28 12:43   ` Ludovic Courtès
2021-09-28 15:23     ` Xinglu Chen

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=87o88aoan1.fsf@trop.in \
    --to=andrew@trop.in \
    --cc=go.wigust@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=public@yoctocell.xyz \
    /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.