From: Arne Babenhauserheide <arne_bab@web.de>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Arne Babenhauserheide <arne_bab@web.de>,
guile-devel <guile-devel@gnu.org>
Subject: Re: What is needed in guildhall to include it in Guile?
Date: Tue, 23 Feb 2016 17:57:14 +0100 [thread overview]
Message-ID: <87fuwj1hjq.fsf@web.de> (raw)
In-Reply-To: <1456163829.7330.32.camel@Renee-desktop.suse>
So, to summarize the things I can change:
- Add the path to the installed package in guild show <package> or list-packages
- Add a dynamical site as repository
- Package guix features
- Package guildhall in guix
And things I can’t change easily:
- Package many packages (I hope a site with easy uploads could change that)
- Add dynamically fetched packages (I’m not sure how to do that right —
or whether I actually want to do it, given that this means executing
code which is downloaded at runtime…)
Requirements for a guildhall website:
- easy upload (like marmalade?)
- download statistics
- bug reporting possible (maybe a link to a bugtracker?)
Did I miss something?
Nala Ginrut writes:
> I may anticipate the packages amount for Guile would be increasing if we
> done it properly.
I’d think so, too.
Best wishes,
Arne
next prev parent reply other threads:[~2016-02-23 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 15:08 What is needed in guildhall to include it in Guile? Arne Babenhauserheide
2016-02-22 17:57 ` Nala Ginrut
2016-02-23 16:57 ` Arne Babenhauserheide [this message]
2016-02-23 22:50 ` Arne Babenhauserheide
2016-03-23 19:32 ` Arne Babenhauserheide
2016-03-23 22:54 ` Christopher Allan Webber
2017-03-01 19:35 ` Amirouche
2017-03-01 20:34 ` Amirouche
2017-03-03 23:05 ` Amirouche
2016-02-22 18:17 ` Christopher Allan Webber
2016-02-22 19:18 ` Jan Nieuwenhuizen
2016-02-22 20:26 ` Panicz Maciej Godek
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 15:08 Arne Babenhauserheide
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=87fuwj1hjq.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@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.
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).