From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 14.mo4.mail-out.ovh.net ([46.105.40.29] helo=mo4.mail-out.ovh.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1TcyjL-0005MA-3H for openembedded-devel@lists.openembedded.org; Mon, 26 Nov 2012 14:28:11 +0100 Received: from mail413.ha.ovh.net (b9.ovh.net [213.186.33.59]) by mo4.mail-out.ovh.net (Postfix) with SMTP id 04A7F10503BF for ; Mon, 26 Nov 2012 11:56:36 +0100 (CET) Received: from b0.ovh.net (HELO queueout) (213.186.33.50) by b0.ovh.net with SMTP; 26 Nov 2012 12:48:39 +0200 Received: from pac33-2-82-240-38-71.fbx.proxad.net (HELO eb-e6520) (eric%eukrea.com@82.240.38.71) by ns0.ovh.net with SMTP; 26 Nov 2012 12:48:37 +0200 Date: Mon, 26 Nov 2012 11:48:36 +0100 From: Eric =?ISO-8859-1?B?QuluYXJk?= To: openembedded-devel@lists.openembedded.org X-Ovh-Mailout: 178.32.228.4 (mo4.mail-out.ovh.net) Message-ID: <20121126114836.4d72ab9e@eb-e6520> In-Reply-To: <50B34831.10402@communistcode.co.uk> References: <1353864310-20097-1-git-send-email-eric@eukrea.com> <1353864310-20097-7-git-send-email-eric@eukrea.com> <50B3440E.9080600@communistcode.co.uk> <20121126113056.6385c072@eb-e6520> <50B34831.10402@communistcode.co.uk> Organization: =?ISO-8859-1?B?RXVrculh?= Electromatique X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.8; x86_64-redhat-linux-gnu) Mime-Version: 1.0 X-Ovh-Tracer-Id: 5261611741099896137 X-Ovh-Remote: 82.240.38.71 (pac33-2-82-240-38-71.fbx.proxad.net) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-OVH-SPAMSTATE: OK X-OVH-SPAMSCORE: 0 X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeehgedrvdehucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecunecuhfhrohhmpefgrhhitgcuueornhgrrhguuceovghrihgtsegvuhhkrhgvrgdrtghomheqnecuffhomhgrihhnpehhihgrfigrthhhrgdqfigvsghsvghrvhgvrhdrohhrghenucfjughrpeffhffvuffkjghfohfogggtgfesthhqredtredtud X-Spam-Check: DONE|U 0.5/N X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeehgedrvdehucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecunecuhfhrohhmpefgrhhitgcuueornhgrrhguuceovghrihgtsegvuhhkrhgvrgdrtghomheqnecuffhomhgrihhnpehhihgrfigrthhhrgdqfigvsghsvghrvhgvrhdrohhrghenucfjughrpeffhffvuffkjghfohfogggtgfesthhqredtredtud Subject: Re: [meta-webserver][PATCH 7/7] hiawatha: add CONFFILES and a php example X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 13:28:11 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Le Mon, 26 Nov 2012 10:45:05 +0000, Jack Mitchell a =E9crit : > On 26/11/12 10:30, Eric B=E9nard wrote: > > Hi Jack, > > > > Le Mon, 26 Nov 2012 10:27:26 +0000, > > Jack Mitchell a =E9crit : > > > >> On 25/11/12 17:25, Eric B=E9nard wrote: > >>> + # configure php-fcgi to have a working configuration > >>> + # by default if php is installed > >>> + echo "Server =3D ${bindir}/php-cgi ; 2 ; 127.0.0.1:2005 ; nobody= :nobody ; ${sysconfdir}/php/hiawatha-php5/php.ini" >> ${D}${sysconfdir}/hia= watha/php-fcgi.conf > >>> } > >> Looks good to me, thanks for the improvements Eric! > >> > > I still have to find a good way to provide a default > > ${sysconfdir}/php/hiawatha-php5/php.ini and launch php-fcgi in the init > > script if php is enabled. > > Do you think we could provide the file php.ini in the hiawatha recipe > > (as hiawatha's doc recommends setting some options : > > http://www.hiawatha-webserver.org/howto/php_configuration ) ? > > > > Eric >=20 > The only way I could think of doing it would be to have some sort of=20 > test to see if PHP is installed and then possibly sed the php.ini file=20 > to set the correct values. >=20 > On the other hand, a note in the BB file may be enough and OE users=20 > shouldn't really need their hands holding to this level. >=20 > As for the init file, I use PHP and Hiawatha as normal CGI rather than=20 > using a fastCGI daemon, therefore I don't think it would be appropriate=20 > to automatically start the fcgi daemon. We could possibly ship a=20 > seperate fastCGI init file, although not automatically enable it? yes the idea is to provide default confi/init files which work so that users can enable them with .bbappend in their overlay. Eric