binarycloud-dev

[binarycloud-dev] Little problems with CVS version

[IFEROE <IF...@te...>]

Hi,

Yesterday I did a complete download of binarycloud from CVS. So far, 
I've only found two problems.
The first one is in $BCHOME/base/core/Makefile. Request.php is missing 
from PACKAGEDFILES, so the make doesn't copy it to the build directory.
The second one is in QueryManager.php. In _ProcessResult() method, 
MetabaseGetColumnNames is called with wrong parameters. 
MetabaseGetColumnNames expects three parameters but only two are 
supplied. I've changed this:

$colNames = MetabaseGetColumnNames($this->handle, $_result);

for this:

$colnames = array();
$ok = MetabaseGetColumnNames($this->handle, $_result, $colnames);

and it started to work again.

Regards

Salva


 ___________________________________________________________________ 
Consigue tu e-mail gratuito TERRA.ES
 Haz clic en http://www.terra.es/correo/

RE: [binarycloud-dev] Little problems with CVS version

[Andreas A. <a.a...@th...>]

Hi Salva,

>Yesterday I did a complete download of binarycloud from CVS.
>So far,
>I've only found two problems.
>The first one is in $BCHOME/base/core/Makefile. Request.php is missing
>from PACKAGEDFILES, so the make doesn't copy it to the build directory.

It is still missing? Hmm...


>The second one is in QueryManager.php. In _ProcessResult() method,
>MetabaseGetColumnNames is called with wrong parameters.
>MetabaseGetColumnNames expects three parameters but only two are
>supplied. I've changed this:

Uaahhh, *sigh*, bad, damend s**t. Ok, I've crushed this bug. Thanks for
reporting.


Andi

Re: [binarycloud-dev] Little problems with CVS version

[peter m. <pm...@sp...>]

One problem I've found is that build/en/user/conf is not
world-readable/executable after it's built by make.  So a default 
install results in:


Warning: Failed opening
'/usr/local/r2/binarycloud/build/en/user/conf/Configuration.php' for
inclusion (include_path='.:/usr/local/php4.mod/lib/php') in
/usr/local/r2/binarycloud/build/en/htdocs/prepend.php on line 44
 
Warning: Failed opening
'/usr/local/r2/binarycloud/build/en/user/conf/Languages.php' for inclusion
(include_path='.:/usr/local/php4.mod/lib/php') in
/usr/local/r2/binarycloud/build/en/htdocs/prepend.php on line 44

etc.  This might be intentional -- should those directories be owned by 
nobody?


Peter

Re: [binarycloud-dev] Little problems with CVS version

[Alex B. <en...@tu...>]

> One problem I've found is that build/en/user/conf is not
> world-readable/executable after it's built by make.  So a default
> install results in:
> 
> 
> Warning: Failed opening
> '/usr/local/r2/binarycloud/build/en/user/conf/Configuration.php' for
> inclusion (include_path='.:/usr/local/php4.mod/lib/php') in
> /usr/local/r2/binarycloud/build/en/htdocs/prepend.php on line 44
> 
> Warning: Failed opening
> '/usr/local/r2/binarycloud/build/en/user/conf/Languages.php' for inclusion
> (include_path='.:/usr/local/php4.mod/lib/php') in
> /usr/local/r2/binarycloud/build/en/htdocs/prepend.php on line 44
> 
> etc.  This might be intentional -- should those directories be owned by
> nobody?

No, but if you're running as shared installation it's a good idea to keep
your source and build trees accessible to a group that has your user and the
webserver user.

Note that make does not currently modify permissions, I had thought about
making that one of the options in MakeConf... we'll see :)

best,

_alex

RE: [binarycloud-dev] Little problems with CVS version

[Andreas A. <a.a...@th...>]

Hi Peter,

>One problem I've found is that build/en/user/conf is not
>world-readable/executable after it's built by make.  So a default
>install results in:
Hmm.

>etc.  This might be intentional -- should those directories be owned by
>nobody?

I think this is up to the user. The only requirements the files must match
is "readabel by webserver" and for the cache directory also writable. If you
use nobody/nobody root/root, apache/apache or foo/bar is up to you.

Andi