From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Barry Fishman <barry@ecubist.org>
Cc: guile-user@gnu.org
Subject: Re: Guile-Config 0.1 Released
Date: Wed, 17 Feb 2016 18:33:23 +0100 [thread overview]
Message-ID: <877fi3xmvw.fsf@gmail.com> (raw)
In-Reply-To: <m3lh6jwa95.fsf@ecube.ecubist.org>
Hi Barry,
Barry Fishman writes:
> On 2016-02-17 08:43:43 +0100, Alex Sassmannshausen wrote:
>> Arne Babenhauserheide writes:
>>> Is there a recommended way to use this in my project when my users don’t
>>> use Guix?
>>
>> You should be able to do the usual GNU installation procedure of:
>> - download tarball
>> - untar
>> - run ./configure && make && make install
>>
>> You may need to install some additional build tools for this, but
>> outside build tools the only dependency should be guile.
>>
>> HTH, let me know if you run into problems with that :-)
>
> Is there a public repository for this software?
As per my original email, the public repository is currently hosted on
github at:
https://github.com/a-sassmannshausen/guile-config
> The configure fails on any guile 2.1. Part of the problem seems to be
> that configure script does not like to put stuff under 2.2 but just 2.0.
huh. Interesting. Thanks for testing, I'll look into that in the near
future.
> After installing in 2.0.11, I found that the Texinfo file had:
>
> @dircategory Guile
> @direntry
> * Guile Config: (Config). Declarative program configuration
> @end direntry
>
> but the info file is not Config or Config.info, but conf.info.
Quite right — that is an oversight on my part due to some recent
namespace changing. I've made a new release tarball and uploaded it to
the site.
The URL for it is:
http://alex.pompo.co/software/guile-config-0.1.1.tar.gz
> As a general side note, not specific to this modules:
>
> [...]
I certainly sympathise with the perspective that packaging Guile modules
is currently… cumbersome. Unfortunately I do not feel qualified to say
much beyond that, as I don't understand build systems well enough.
I'll leave to others, more knowledgeable than I am, to comment on these
thoughts.
Thanks for testing, and for your feedback!
Best wishes,
Alex
prev parent reply other threads:[~2016-02-17 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 9:19 Guile-Config 0.1 Released Alex Sassmannshausen
2016-02-17 7:28 ` Arne Babenhauserheide
2016-02-17 7:43 ` Alex Sassmannshausen
2016-02-17 16:51 ` Barry Fishman
2016-02-17 17:33 ` Alex Sassmannshausen [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://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=877fi3xmvw.fsf@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--cc=barry@ecubist.org \
--cc=guile-user@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.
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).