From: ludo@gnu.org (Ludovic Courtès)
To: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
Cc: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>,
guix-devel@gnu.org, Alex Sassmannshausen <alex@pompo.co>
Subject: Re: [PATCH 1/1] gnu: Add Guile-ICS.
Date: Sun, 08 Jan 2017 23:45:26 +0100 [thread overview]
Message-ID: <87r34dqigp.fsf@gnu.org> (raw)
In-Reply-To: <87mvf1eh0g.fsf@gmail.com> (Artyom V. Poptsov's message of "Sun, 08 Jan 2017 17:57:35 +0300")
Artyom V. Poptsov <poptsov.artyom@gmail.com> skribis:
> Hello Ludovic and Alex.
Hey Artyom!
>> Cool, we’ll be able to browse the FOSDEM schedule from Guile! :-)
>
> Yes, for that matter I preparted a script that exports the FOSDEM
> schedule to org-mode format:
> https://github.com/artyom-poptsov/guile-ics/blob/master/examples/fosdem.scm.in
>
> You can use it as an example.
Yes, I saw it and I like the idea. :-)
>> Apparently 0.1.1 is already out!
>
> Alas, as it turns out I overlooked one of dependencies on 'guile-lib'.
> I'll fix it in the next release but for now it requires 'guile-lib' as
> one of the inputs.
That’s OK.
>> But it might be best to just download from github.com and add a
>> bootstrap phase, like I did for Guile-SSH, because memory-heap.org is
>> slow and sometimes disappeared in the past.
>
> memory-heap.org is my personal home server that sometimes is not
> accessible for the public due to problems with dynamic DNS updating
> mechanism, so using github.com is more robust approach.
Thanks for confirming.
Cheers,
Ludo’.
next prev parent reply other threads:[~2017-01-08 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 21:25 [PATCH 0/1] Add Guile-ICS Alex Sassmannshausen
2017-01-07 21:25 ` [PATCH 1/1] gnu: " Alex Sassmannshausen
2017-01-08 11:09 ` Ludovic Courtès
2017-01-08 14:57 ` Artyom V. Poptsov
2017-01-08 22:45 ` Ludovic Courtès [this message]
2017-01-09 10:37 ` Alex Sassmannshausen
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=87r34dqigp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alex.sassmannshausen@gmail.com \
--cc=alex@pompo.co \
--cc=guix-devel@gnu.org \
--cc=poptsov.artyom@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 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).