all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Prafulla Giri <pratheblackdiamond@gmail.com>
Cc: 39049@debbugs.gnu.org
Subject: [bug#39049] guix-install.sh: Create an init profile for better out-of-the-box experience on foreign distros
Date: Mon, 20 Jan 2020 09:38:32 +0100	[thread overview]
Message-ID: <874kwqjzef.fsf@gnu.org> (raw)
In-Reply-To: <CAFw+=j1GvNd0Mi1q5cB9W11gsgZ42HTMD=r_Y=_ZW7wYThfA_Q@mail.gmail.com> (Prafulla Giri's message of "Sun, 19 Jan 2020 22:39:13 +0545")

Hello,

Prafulla Giri <pratheblackdiamond@gmail.com> skribis:

> /etc/profile.d/*.sh seems to be the norm these days. All the debian-based
> distros that I have used seem to have it (Mint, Elementary, Ubuntu, etc.)
> and even Alpine Linux's docker containers support them.

OK, great.

> I didn't  really think this patch will get merged in one go. I did find
> another thing that I could add to this patch  the other day but had not
> gotten around to updating this. It is regarding the infopath: setting it to
> contain _GUIX_PROFILE/share/info seems to be a good default to have, esp.
> because it isn't exported by `guix package --search-paths`. I ran into this
> issue just the other day, myself. I wish I had made haste to send in an
> update.

I agree that it’d be nice!

> Should I send in a patch, sir? And do I send it in this thread or should I
> do it in another one, please?

Could you send another patch to guix-patches@gnu.org?

Thank you,
Ludo’.

      parent reply	other threads:[~2020-01-20  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  7:23 [bug#39049] guix-install.sh: Create an init profile for better out-of-the-box experience on foreign distros Prafulla Giri
2020-01-17 16:29 ` Ludovic Courtès
     [not found]   ` <CAFw+=j1GvNd0Mi1q5cB9W11gsgZ42HTMD=r_Y=_ZW7wYThfA_Q@mail.gmail.com>
2020-01-20  8:38     ` Ludovic Courtès [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

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

  git send-email \
    --in-reply-to=874kwqjzef.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39049@debbugs.gnu.org \
    --cc=pratheblackdiamond@gmail.com \
    /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.