all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: [PATCH] Add php
Date: Thu, 17 Nov 2016 20:38:43 +0100	[thread overview]
Message-ID: <20161117203843.68f675f1@lepiller.eu> (raw)
In-Reply-To: <582D84FD.5010500@crazy-compilers.com>

On Thu, 17 Nov 2016 11:22:53 +0100
Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:

> Am 17.11.2016 um 01:01 schrieb Marius Bakke:
> > If there are no further comments, I will push this in the next few
> > days:  
> 
> Thanks for your work on this. It seems to be laborious.
> 
> I don't have time to inspect not to test the patch, so just some
> thought. I'm not a php-user, but wanted to install a php-driven
> website on Guix some weeks ago and had a look on what else would be
> required.
> 
>   * Does this php package include what other distributions call
>     "php-cli", "php-fpm" and "php-cgi"? Maybe you want to mention it
> in the synopsis. (Addendum: I just found in
>     <https://packages.debian.org/source/jessie/php5> that it looks
> like these are part of the package.)
>   * As far as I understood, "pear" and "pecl" are important for
>     installing php packages. Are these part of your package, too?

The package contains the following executables in sbin and bin:
php-fpm  pear  peardev  pecl  phar  phar.phar  php  php-cgi  php-config
phpdbg  phpize

> 
> 
>   * What do you think about adding "Packaging guideline" for "PHP
>     Modules" section to the manual?
>   * Do yo think we need some php build system?
I have no idea how system-wide php packages could be installed, so I
can't answer that (yet?). Sorry.

> 
> 

  reply	other threads:[~2016-11-17 19:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 12:08 [PATCH] Add php Julien Lepiller
2016-10-30 14:01 ` Efraim Flashner
2016-10-30 14:03 ` Tobias Geerinckx-Rice
2016-10-30 16:51   ` Julien Lepiller
2016-10-30 22:24     ` Ludovic Courtès
2016-10-30 23:17     ` Marius Bakke
2016-11-02 21:40       ` Julien Lepiller
2016-11-09 15:44         ` Ludovic Courtès
2016-11-11 16:31           ` Julien Lepiller
2016-11-14  9:48             ` Marius Bakke
2016-11-14  9:57               ` Marius Bakke
2016-11-14 12:59                 ` Ludovic Courtès
2016-11-14 13:53                   ` Marius Bakke
2016-11-14 14:46                     ` Ludovic Courtès
2016-11-17  0:01                       ` Marius Bakke
2016-11-17 10:22                         ` Hartmut Goebel
2016-11-17 19:38                           ` Julien Lepiller [this message]
2016-11-17 11:08                         ` tyreunom
2016-11-17 12:27                           ` Ludovic Courtès
2016-11-17 18:22                           ` Marius Bakke
2016-11-17 19:34                             ` Julien Lepiller
2016-11-17 20:43                               ` Marius Bakke
2016-11-18 17:25                                 ` Julien Lepiller
2016-11-18 18:09                                   ` Marius Bakke
2016-11-20 17:02                                     ` Marius Bakke
2016-11-20 17:13                                       ` Leo Famulari
2016-11-21  8:46                                       ` Ludovic Courtès
2016-11-01 17:07 ` Leo Famulari

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=20161117203843.68f675f1@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@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.