From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add php-hello-world.
Date: Thu, 29 Dec 2016 18:44:51 +0100 [thread overview]
Message-ID: <87inq2fx4c.fsf@gnu.org> (raw)
In-Reply-To: <2d4d2802-cf2f-d61c-c286-6d2ae0012ce9@crazy-compilers.com> (Hartmut Goebel's message of "Thu, 22 Dec 2016 18:43:36 +0100")
Hi Hartmut!
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> Am 21.12.2016 um 17:38 schrieb Ludovic Courtès:
>> For other tools we provide what upstream provides. For example, Qt
>> comes with examples, which we provide in the ‘qt’ package (IIRC).
>
> The php source package does not provide any example. I also searched the
> internet for some hello-world-package, but did not find one.
>
> If you know of one, feel free to replace this one.
>
> If you dislike "home-made" packages so much, I can set up a
> "php-hello-world" project at github. But what should be the benefit?
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.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2016-12-29 17:44 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 [this message]
2016-12-29 19:20 ` Hartmut Goebel
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=87inq2fx4c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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 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.