From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Pjotr Prins <pjotr.public12@thebird.nl>,
Catonano <catonano@gmail.com>, guix-devel <guix-devel@gnu.org>,
"Frederick M. Muriithi" <fredmanglis@protonmail.com>
Subject: Re: Rails
Date: Fri, 14 Jul 2017 19:42:10 +1000 [thread overview]
Message-ID: <cfa86424-f4e4-a16f-e2fe-376d7f21f77f@uq.edu.au> (raw)
In-Reply-To: <20170712084716.sr5h6r6khwkxnuup@abyayala>
On 12/07/17 18:47, ng0 wrote:
> Pjotr Prins transcribed 0.4K bytes:
>> On Wed, Jul 12, 2017 at 08:03:48AM +0000, ng0 wrote:
>>> While I was working on it (or occasionally do) I wonder why we have so
>>> little rails packages? What happened there?
>> Ruby support is great in Guix. But we don't use Rails much, yet. Dave
>> started packaging some time back, but not sure what happened. We also
>> need it for Arvados - Fred is working on that.
>>
>> Pj.
>>
>>
> Ah! Good to know. I have some packages in a dirty branch, I just need to
> figure out the right order. at the moment it's just one file and the top
> view are about 40 rails packages I guess.
There is actually a branch wip-rails on savannah that boots rails. It is
somewhat dated, and needs some overall work (removal of unused packages,
to start). Help is welcome - I won't be able to get to this for a few
months at least.
Many of the packages you list ng0 are in that branch, or already in Guix.
ben
next prev parent reply other threads:[~2017-07-14 9:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 7:19 self hosting hardware Catonano
2017-07-12 7:22 ` Catonano
2017-07-12 8:03 ` ng0
2017-07-12 8:20 ` Rails Pjotr Prins
2017-07-12 8:47 ` Rails ng0
2017-07-14 9:42 ` Ben Woodcroft [this message]
2017-07-12 8:53 ` self hosting hardware Catonano
2017-07-12 13:34 ` Ricardo Wurmus
2017-07-14 8:44 ` Catonano
2017-07-12 9:06 ` Solène Rapenne
2017-07-12 10:48 ` Catonano
2017-07-12 12:40 ` Pjotr Prins
2017-07-12 14:37 ` Solène Rapenne
2017-07-12 15:03 ` Vincent Legoll
2017-07-14 8:47 ` Catonano
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=cfa86424-f4e4-a16f-e2fe-376d7f21f77f@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=catonano@gmail.com \
--cc=fredmanglis@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.