Re: WP-CLI

2016-02-22 Thread Ryan Schmidt 

On Feb 22, 2016, at 3:00 AM, Takeshi Enomoto wrote:

> - The script in phar does not require the extract phase. Can I
> destroot directly from ${distpath}?

Yes, but instead of overriding the extract phase with

extract {}

it is preferred to clear the extract.only variable with

extract.only


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: WP-CLI

2016-02-22 Thread Ryan Schmidt 
On Feb 22, 2016, at 4:24 PM, Joshua Root wrote:

> On 2016-2-22 20:00 , Takeshi Enomoto wrote:
>> Hi,
>> 
>> I created a Portfile for WP-CLI,
>> which is very useful installing and managing WordPress sites.
>> 
>> 
>> 
>> It is just a compressed PHP script so it might not worth packaging,
>> but Homebrew has a formula and it is mentioned at the WP-CLI web site
>> as and alternative method to install.
>> So I thought we should also provide a Portfile.
>> 
>> - The script runs with php that it finds. Is this OK?
> 
> If it works fine with any version of php this may be OK. If not,
> variants adding a dependency on different php ports may be appropriate.

The other reason to use a specific PHP version (i.e. with variants) is if this 
script needs a PHP module that would be installed with MacPorts. If it needs no 
modules, and works with any version of PHP, then no need for a MacPorts PHP 
dependency.


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: WP-CLI

2016-02-22 Thread Takeshi Enomoto 
Dear Sterling and Joshua,

Thank you for response.

I could have commit the port, but I don't have enough experience with PHP ports.
So I asked for advice.

> If it works fine with any version of php this may be OK. If not,
> variants adding a dependency on different php ports may be appropriate.
> Does this script need to use the same php as the wordpress installation
> it manages?

I don't think you need the same version.

BTW our wordpress port is out of date.
WP-CLI installs the newest version by default,
we don't have to maintain this port.

---
Takeshi Enomoto
take...@macports.org
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: WP-CLI

2016-02-22 Thread Joshua Root 
On 2016-2-22 20:00 , Takeshi Enomoto wrote:
> Hi,
> 
> I created a Portfile for WP-CLI,
> which is very useful installing and managing WordPress sites.
> 
> 
> 
> It is just a compressed PHP script so it might not worth packaging,
> but Homebrew has a formula and it is mentioned at the WP-CLI web site
> as and alternative method to install.
> So I thought we should also provide a Portfile.
> 
> - The script runs with php that it finds. Is this OK?

If it works fine with any version of php this may be OK. If not,
variants adding a dependency on different php ports may be appropriate.
Does this script need to use the same php as the wordpress installation
it manages?

> - The script in phar does not require the extract phase. Can I
> destroot directly from ${distpath}?

Yes, that's fine.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: WP-CLI

2016-02-22 Thread Sterling Smith 
I suspect someone will ask you to open a ticket for this, which is the usual 
method for asking for a new port.

-Sterling

On Feb 22, 2016, at 1:00AM, Takeshi Enomoto  wrote:

> Hi,
> 
> I created a Portfile for WP-CLI,
> which is very useful installing and managing WordPress sites.
> 
> 
> 
> It is just a compressed PHP script so it might not worth packaging,
> but Homebrew has a formula and it is mentioned at the WP-CLI web site
> as and alternative method to install.
> So I thought we should also provide a Portfile.
> 
> - The script runs with php that it finds. Is this OK?
> - The script in phar does not require the extract phase. Can I
> destroot directly from ${distpath}?
> 
> ---
> Takeshi Enomoto
> take...@macports.org
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev