"Stuart Herbert" <[EMAIL PROTECTED]> writes:
>> But it is not very hard to avoid to hardwire these libs in your
>> webapp :) This is the only thing I dislike.
>
> Mmm ... you'd be surprised, I think, about just how hard it actually is
> for PHP apps (and how expensive it is too).
Guess I'm missing the point here. What I meant was to change stuff like this:
require_once(HOME . "/thirdparty/Smarty/Smarty.class.php");
to something like this:
$include_path = ini_get('include_path');
ini_set('include_path', HOME . '/thirdparty' . SEPARATOR . $include_path);
require_once('Smarty/Smarty.class.php');
What is the negative side of such a change?
> Another problem to consider is versioning of any shared libraries of
> code. How do you plan to address that, in a non-Gentoo-specific way?
Where is the difference to C or Java? The recent xpdf discussion
basically touched the same issue, right? Packaging precompiled
binaries into java source packages is a common practice but has been
effictively banned by the java herd. Sometimes necessitates larger
changes in the build scripts for the app but I guess it increases
maintainability in the long run.
Where is the difference for the php libraries?
Best regards,
Gunnar
--
Gunnar Wrobel Gentoo Developer
__________________C_o_n_t_a_c_t__________________
Mail: [EMAIL PROTECTED]
WWW: http://www.gunnarwrobel.de
IRC: #gentoo-web at freenode.org
_________________________________________________
--
[email protected] mailing list
