All files from this thread

File Name	File Size		Posted by	Date
php.tar.bz2	10.5 KB	open | download	Vasiliy G Tolstov	10/14/2009	Read message

Модифицированнй ebuild, ставит fpm как sapi (по аналогии с cli и cgi),
плюс вроде как должен стабильнее suhosin работать (используется уже не
бета версия для 5.3)
Никаких патчей.

Может уже пробегало тут но мало ли...


Modification to php-5.3.0.ebuild to install fpm like other php sapi (cli
or cgi). Nothing needed to patch.


--
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru

That will be very useful. Thanks. Have you filed it in Gentoo's Bugzilla?

2009/10/14 Vasiliy G Tolstov <v.tolstov@selfip.ru>:
> Модифицированнй ebuild, ставит fpm как sapi (по аналогии с cli и cgi),
> плюс вроде как должен стабильнее suhosin работать (используется уже не
> бета версия для 5.3)
> Никаких патчей.
>
> Может уже пробегало тут но мало ли...
>
>
> Modification to php-5.3.0.ebuild to install fpm like other php sapi (cli
> or cgi). Nothing needed to patch.
>
>
> --
> Vasiliy G Tolstov <v.tolstov@selfip.ru>
> Selfip.Ru
>

Hi,
Please be aware that md5 checksum verification will fail for the
official launchpad download link. This is because we have a policy to
upload newer versions under the same filename. Its nothing to worry
about.

The next changes will improve the 'make install' command.

* Fix Missing dependency operator (freebsd)
* Install nginx sample config file
* --without-fpm-conf (no install) option
* Rename php-fpm.conf to php-fpm.conf.old
* Symlink php-fpm.conf -> php-fpm.conf.default
* Default /usr/local/etc/rc.d/php-fpm for freebsd (thanks kheechin)
* Default paths for netbsd, openbsd, arch linux
* Don't install init script for openbsd
* Installation notes, tips (readme.markdown)
* Regenerated with ./buildconf

We hope it will not affect your ebuild. I just thought you should know
incase of any possible breakages.


best regards

dreamcat4
dreamcat4@gmail.com

That will also break the FreeBSD port, not only that its very
confusing from even a basic user perspective, i.e. I downloaded that
version why would I ever look to download it again?

Given this I would strongly encourage you to create a new download for
each version.

Hi,

On Wed, Oct 14, 2009 at 3:16 PM, steven.hartland
<steven.hartland@multiplay.co.uk> wrote:
>
> That will also break the FreeBSD port, not only that its very

You can just turn of the md5 hash check in your port to circumvent the issue.

> confusing from even a basic user perspective, i.e. I downloaded that
> version why would I ever look to download it again?
>
> Given this I would strongly encourage you to create a new download for
> each version.

Yeah its down to a combination of factors why we do this. For example
it would still be confusing if we were to host all such minor versions
on launchpad. With 4+ files per release, and a version numbering
scheme which is excessively long. We do however print the VCS revision
number and the date next to each file. That isn't terrific, but it
isn't too bad either.

However we will consult with launchpad / canoical on this. They might
have ideas about how to organise the downloads page / per release
downloads section. Its not a high priority as you might think whilst
we are filing for a merge with the official php sources.

Also we arent making and significant runtime changes for fpm 0.6, only
minor patch-level updates. So to answer your question, we hope you
won't care to upgrade until there is an new major release number. By
that time we hope to have properly solved such download issues.


Best regards,

dreamcat4
dreamcat4@gmail.com

Nope checksums are a requirement.

You don't have to list all the files, they just need to always be
available. Id suggest list the latest in 0.X series for example 0.6.4

On Wed, Oct 14, 2009 at 4:36 PM, steven.hartland
<steven.hartland@multiplay.co.uk> wrote:
>
> Nope checksums are a requirement.
>
> You don't have to list all the files, they just need to always be
> available. Id suggest list the latest in 0.X series for example 0.6.4

Okay, i have just discussed with Canoical / Launchpad support team.
We may be able to support this soon.

Due to the way we create out tarballs, its likely that these archived
versions will be pre-pended with the revision number from version
control, in conjunction with the major version number. The VCS
revision number is just an incremented number.

So it would probably be some concactenation of
fpm-0.6 + $PHP_VER + r$BZR_REV



Best regards,

dreamcat4
dreamcat4@gmail.com

В Срд, 14/10/2009 в 08:49 -0500, Gordon Pettey пишет:
> That will be very useful. Thanks. Have you filed it in Gentoo's Bugzilla?

No, i don't have enouth time, but You can do it =)

--
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru

В Срд, 14/10/2009 в 16:05 +0100, dreamcat four пишет:
> Hi,
>
> On Wed, Oct 14, 2009 at 3:16 PM, steven.hartland
> <steven.hartland@multiplay.co.uk> wrote:
> >
> > That will also break the FreeBSD port, not only that its very
>
> You can just turn of the md5 hash check in your port to circumvent the issue.
>
> > confusing from even a basic user perspective, i.e. I downloaded that
> > version why would I ever look to download it again?
> >
> > Given this I would strongly encourage you to create a new download for
> > each version.
>
> Yeah its down to a combination of factors why we do this. For example
> it would still be confusing if we were to host all such minor versions
> on launchpad. With 4+ files per release, and a version numbering
> scheme which is excessively long. We do however print the VCS revision
> number and the date next to each file. That isn't terrific, but it
> isn't too bad either.
>
> However we will consult with launchpad / canoical on this. They might
> have ideas about how to organise the downloads page / per release
> downloads section. Its not a high priority as you might think whilst
> we are filing for a merge with the official php sources.
>
> Also we arent making and significant runtime changes for fpm 0.6, only
> minor patch-level updates. So to answer your question, we hope you
> won't care to upgrade until there is an new major release number. By
> that time we hope to have properly solved such download issues.
>

Ok, please tag releases in github - i rewrite port to get data from here
=)


--
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru

В Срд, 14/10/2009 в 15:01 +0100, dreamcat four пишет:
> Hi,
> Please be aware that md5 checksum verification will fail for the
> official launchpad download link. This is because we have a policy to
> upload newer versions under the same filename. Its nothing to worry
> about.

This breaks ebuild for users, who using portage packages manager (i'm
usin paludis and silently ignore checksum. Can You provide new versions
with different name (like -r1...-r10).

>
> The next changes will improve the 'make install' command.
>
> * Fix Missing dependency operator (freebsd)
> * Install nginx sample config file
> * --without-fpm-conf (no install) option

Sample file need rewrite :
http://github.com/dreamcat4/php-fpm/blob/master/conf/nginx-site-conf.sample.in

set $site_root /var/www/nginx-site; does not needed, becouse nginx have
root directive (root /var/www/nginx-site;)


location / {
root $site_root; !!! does not needed, becouse we defined it early
(replace set $site_root with root)
index index.html index.htm;
}


location ~ \.php$ {

root $site_root; !!! does not needed because root is defined early
fastcgi_pass 127.0.0.1:@php_fpm_port@;
fastcgi_index index.php;

include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root
$fastcgi_script_name;
fastcgi_param SERVER_NAME $http_host;
fastcgi_ignore_client_abort on;
}


> * Rename php-fpm.conf to php-fpm.conf.old
> * Symlink php-fpm.conf -> php-fpm.conf.default
> * Default /usr/local/etc/rc.d/php-fpm for freebsd (thanks kheechin)
> * Default paths for netbsd, openbsd, arch linux
> * Don't install init script for openbsd
> * Installation notes, tips (readme.markdown)
> * Regenerated with ./buildconf
>
> We hope it will not affect your ebuild. I just thought you should know
> incase of any possible breakages.


--
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru

On Thu, Oct 15, 2009 at 6:53 AM, Vasiliy G Tolstov <v.tolstov@selfip.ru> wrote:
> set $site_root  /var/www/nginx-site; does not needed, becouse nginx have
> root directive (root /var/www/nginx-site;)
>
>
>        location / {
>                root   $site_root; !!! does not needed, becouse we defined it early
> (replace set $site_root with root)
>                index  index.html index.htm;
>        }
>
>
>        location ~ \.php$ {
>
>                root $site_root; !!! does not needed because root is defined early
>                fastcgi_pass   127.0.0.1:@php_fpm_port@;
>                fastcgi_index  index.php;
>
>                include fastcgi_params;
>        fastcgi_param SCRIPT_FILENAME $document_root
> $fastcgi_script_name;
>        fastcgi_param SERVER_NAME $http_host;
>        fastcgi_ignore_client_abort on;
>        }
>
>
Im not sure i understand the suggestion because you seem to be saying
replacing "root $site_root;" with "root root;" which should throw an
error. There are seprate location blocks for the static and php, in
case someone chooses their php files in a seperate cgi-bin directory.
So this is correct. The root is set on a per site-file basis simply
because we do not know what is written in the main nginx.conf. So this
is correct.

It may be the case that the root directive is already set (and we
expect that for certain nginx distro / package). But in other cases
the nginx.conf do not, including debian and ubuntu .deb packages,
where its defined seperately in per-site file. So we write the
directive because it's not going to throw an error this way,
regardless of your existing nginx.conf. As this is a samply
configuration file, its expected to tweak it / modify it to suit your
specific needs.


Best regards,

dreamcat4
dreamcat4@gmail.com

В Чтв, 15/10/2009 в 10:15 +0100, dreamcat four пишет:
> On Thu, Oct 15, 2009 at 6:53 AM, Vasiliy G Tolstov <v.tolstov@selfip.ru> wrote:
> > set $site_root /var/www/nginx-site; does not needed, becouse nginx have
> > root directive (root /var/www/nginx-site;)
> >
> >
> > location / {
> > root $site_root; !!! does not needed, becouse we defined it early
> > (replace set $site_root with root)
> > index index.html index.htm;
> > }
> >
> >
> > location ~ \.php$ {
> >
> > root $site_root; !!! does not needed because root is defined early
> > fastcgi_pass 127.0.0.1:@php_fpm_port@;
> > fastcgi_index index.php;
> >
> > include fastcgi_params;
> > fastcgi_param SCRIPT_FILENAME $document_root
> > $fastcgi_script_name;
> > fastcgi_param SERVER_NAME $http_host;
> > fastcgi_ignore_client_abort on;
> > }
> >
> >
> Im not sure i understand the suggestion because you seem to be saying
> replacing "root $site_root;" with "root root;" which should throw an
> error. There are seprate location blocks for the static and php, in
> case someone chooses their php files in a seperate cgi-bin directory.
> So this is correct. The root is set on a per site-file basis simply
> because we do not know what is written in the main nginx.conf. So this
> is correct.

Hm... I mean that set $site_root variable does not needed if use root
directive (root /var/www/nginx-site; can be defined at server and
location) if it defined on server and location use this root - does not
need to provide this (it inherited from above level)

>
> It may be the case that the root directive is already set (and we
> expect that for certain nginx distro / package). But in other cases
> the nginx.conf do not, including debian and ubuntu .deb packages,
> where its defined seperately in per-site file. So we write the
> directive because it's not going to throw an error this way,
> regardless of your existing nginx.conf. As this is a samply
> configuration file, its expected to tweak it / modify it to suit your
> specific needs.
>
>
> Best regards,
>
> dreamcat4
> dreamcat4@gmail.com

--
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru

On Thu, Oct 15, 2009 at 10:21 AM, Vasiliy G Tolstov <v.tolstov@selfip.ru> wrote:
> Hm... I mean that set $site_root variable does not needed if use root
> directive (root /var/www/nginx-site; can be defined at server and
> location) if it defined on server and location use this root - does not
> need to provide this (it inherited from above level)
>

Ah okay. We can change that, because it seems very few people uses
cgi-bin/ anymore. Thank you for pointing it out.

>>
>>
>> Best regards,
>>
>> dreamcat4
>> dreamcat4@gmail.com
>
> --
> Vasiliy G Tolstov <v.tolstov@selfip.ru>
> Selfip.Ru
>
>