unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: James Crake-Merani <james@jamescm.co.uk>
To: Munyoki Kilyungi <me@bonfacemunyoki.com>
Cc: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
	adriano <randomlooser@riseup.net>,
	guile-user@gnu.org
Subject: Re: Scripting for installing a module
Date: Tue, 5 Jul 2022 10:46:49 +0100	[thread overview]
Message-ID: <20220705094649.k2sm7v63z62b7ys5@jamescrake-meraniarch> (raw)
In-Reply-To: <868rp8t1rf.fsf@bonfacemunyoki.com>

On 22/07/05 11:14am, Munyoki Kilyungi wrote:
> James Crake-Merani <james@jamescm.co.uk>
> anaandika:
> 
> [...]
> 
> > Hi,
> >
> > The reason why I have been a bit reluctant to use GNU Guix for this
> > sort of thing is that the distro I use is not Guix but rather Arch
> > Linux.
> 
> I run Arch Linux + GNU Guix (as a package manager)
> and it's a nice experience.  I use GNU Guix as my
> primary package manager.  I'd recommend you give
> it a try ;)
> 
> > I do intend to try out GNU Guix in the future but at the moment
> > I have lots of other things to do. I am aware Guix does work on
> > foreign distros but I will need to learn how to use it first.
> >
> > I understand what you say regarding Guile Hall. I too do not
> > understand the autotools machinery but it did seem simple to setup
> > without that understanding. Thanks for sharing your repository.
> >
> 
> Worth mentioning that GNU Guix provides facilities
> for bundling packages using "guix pack".  You
> could provide "tar.gz" files, or even bundle
> things inside docker/squashfs containers for easy
> distribution without requiring your end-user to
> download anything extra. For more read:
> <https://guix.gnu.org/manual/en/html_node/Invoking-guix-pack.html#Invoking-guix-pack>
> 
> [...]
> 
> -- 
> (Life is like a pencil that will surely run out,
>     but will leave the beautiful writing of life.)
> (D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
>     (hkp://keys.gnupg.net))

Hi,

Thanks for letting me know! I will have a look at that.



  reply	other threads:[~2022-07-05  9:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 17:15 Scripting for installing a module James Crake-Merani
2022-07-01 19:50 ` Jérémy Korwin-Zmijowski
2022-07-02  6:32   ` James Crake-Merani
2022-07-02  7:11 ` adriano
2022-07-02  8:46   ` James Crake-Merani
2022-07-02 19:43     ` Zelphir Kaltstahl
2022-07-03  7:35       ` James Crake-Merani
2022-07-03 16:52         ` Zelphir Kaltstahl
2022-07-05  8:14         ` Munyoki Kilyungi
2022-07-05  9:46           ` James Crake-Merani [this message]
2022-07-02 21:09 ` Matt Wette
2022-07-03  7:37   ` james

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=20220705094649.k2sm7v63z62b7ys5@jamescrake-meraniarch \
    --to=james@jamescm.co.uk \
    --cc=guile-user@gnu.org \
    --cc=me@bonfacemunyoki.com \
    --cc=randomlooser@riseup.net \
    --cc=zelphirkaltstahl@posteo.de \
    /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.
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).