all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add php-hello-world.
Date: Thu, 29 Dec 2016 20:20:05 +0100	[thread overview]
Message-ID: <51132cc4-7485-1c54-d9e0-11210b0389e0@crazy-compilers.com> (raw)
In-Reply-To: <87inq2fx4c.fsf@gnu.org>

Am 29.12.2016 um 18:44 schrieb Ludovic Courtès:
> Given the popularity of PHP, I would expect tutorials and examples to
> abound already, no?
>
> You can of course roll your own and Guix could distribute it, that’s
> fine.  I’m just surprised we even have to do that in the first place.

I was surprised, too. Otherwise I'd not write a own package.

But I see no benefit of putting a project to github, just do not have a
"home grown" package at guix. IMHO implementing this is just a waste of
time.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

  reply	other threads:[~2016-12-29 19:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 17:45 [PATCH] gnu: Add php-hello-world Hartmut Goebel
2016-12-08 17:47 ` Hartmut Goebel
2016-12-21 16:38   ` Ludovic Courtès
2016-12-22 17:43     ` Hartmut Goebel
2016-12-29 17:44       ` Ludovic Courtès
2016-12-29 19:20         ` Hartmut Goebel [this message]
2016-12-31 11:16           ` Ludovic Courtès
2016-12-31 12:12             ` Hartmut Goebel
2017-01-04 22:38               ` Ludovic Courtès
2016-12-08 17:52 ` [WIP 0/2] php-fpm service - assistance appreciated Hartmut Goebel
2016-12-08 17:52   ` [WIP 1/2] services: Add php-fpm service Hartmut Goebel
2016-12-08 17:52   ` [WIP 2/2] gnu: Add "PHP FPM" OS config example Hartmut Goebel

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=51132cc4-7485-1c54-d9e0-11210b0389e0@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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. 
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.