From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/6] php-zmq: new package
Date: Tue, 28 Jan 2014 23:16:53 +0100 [thread overview]
Message-ID: <20140128231653.503d0114@skate> (raw)
In-Reply-To: <52E82B2B.5040705@zacarias.com.ar>
Dear Gustavo Zacarias,
On Tue, 28 Jan 2014 19:11:55 -0300, Gustavo Zacarias wrote:
> > Just curious, how many potential PHP packages could we add? The build
> > logic for the four packages you submitted looks highly similar, maybe
> > it calls a php-package infrastructure?
> >
> > The only "difficulty" is that it would have to inherit from
> > autotools-package, which itself already inherits from generic-package.
> > So it would be the first package infrastructure to inherit from a
> > package infra that already inherits from generic-package. I'm sure it
> > can work, but it might raise issues with some missing quoting.
>
> Not that many that are useful, many are abandonware, that being the
> reason i opted for the autotools infra with the tweak.
> PECL packages are compiled (these ones are), PEAR packages are normally
> interpreted so it's just a matter of just installing them.
> Arguably we could also enable PEAR installs in the target itself but i
> don't think it's the spirit of buildroot, like CPAN for perl.
> But we don't have any PEAR packages at the moment.
Ok. Then I guess we should go ahead with what you proposed, and only
introduce a PHP package infra if we get over 10 PHP packages or so.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-28 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 21:26 [Buildroot] [PATCH 1/6] php: security bump to version 5.5.8 Gustavo Zacarias
2014-01-28 21:26 ` [Buildroot] [PATCH 2/6] php: fix for external extensions Gustavo Zacarias
2014-01-30 16:09 ` Peter Korsgaard
2014-01-30 16:16 ` Gustavo Zacarias
2014-01-30 16:40 ` Peter Korsgaard
2014-01-30 17:03 ` Gustavo Zacarias
2014-02-12 18:51 ` Peter Korsgaard
2014-01-28 21:26 ` [Buildroot] [PATCH 3/6] php-zmq: new package Gustavo Zacarias
2014-01-28 22:05 ` Thomas Petazzoni
2014-01-28 22:11 ` Gustavo Zacarias
2014-01-28 22:16 ` Thomas Petazzoni [this message]
2014-01-28 21:26 ` [Buildroot] [PATCH 4/6] php-yaml: " Gustavo Zacarias
2014-01-28 21:26 ` [Buildroot] [PATCH 5/6] php-ssh2: " Gustavo Zacarias
2014-01-28 21:26 ` [Buildroot] [PATCH 6/6] php-imagick: " Gustavo Zacarias
2014-01-28 21:47 ` [Buildroot] [PATCH 1/6] php: security bump to version 5.5.8 Peter Korsgaard
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=20140128231653.503d0114@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 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.