| 1 |
"Stuart Herbert" <Stuart.Herbert@×××××.com> writes: |
| 2 |
|
| 3 |
>> But it is not very hard to avoid to hardwire these libs in your |
| 4 |
>> webapp :) This is the only thing I dislike. |
| 5 |
> |
| 6 |
> Mmm ... you'd be surprised, I think, about just how hard it actually is |
| 7 |
> for PHP apps (and how expensive it is too). |
| 8 |
|
| 9 |
Guess I'm missing the point here. What I meant was to change stuff like this: |
| 10 |
|
| 11 |
require_once(HOME . "/thirdparty/Smarty/Smarty.class.php"); |
| 12 |
|
| 13 |
to something like this: |
| 14 |
|
| 15 |
$include_path = ini_get('include_path'); |
| 16 |
ini_set('include_path', HOME . '/thirdparty' . SEPARATOR . $include_path); |
| 17 |
require_once('Smarty/Smarty.class.php'); |
| 18 |
|
| 19 |
What is the negative side of such a change? |
| 20 |
|
| 21 |
> Another problem to consider is versioning of any shared libraries of |
| 22 |
> code. How do you plan to address that, in a non-Gentoo-specific way? |
| 23 |
|
| 24 |
Where is the difference to C or Java? The recent xpdf discussion |
| 25 |
basically touched the same issue, right? Packaging precompiled |
| 26 |
binaries into java source packages is a common practice but has been |
| 27 |
effictively banned by the java herd. Sometimes necessitates larger |
| 28 |
changes in the build scripts for the app but I guess it increases |
| 29 |
maintainability in the long run. |
| 30 |
|
| 31 |
Where is the difference for the php libraries? |
| 32 |
|
| 33 |
Best regards, |
| 34 |
|
| 35 |
Gunnar |
| 36 |
|
| 37 |
-- |
| 38 |
Gunnar Wrobel Gentoo Developer |
| 39 |
__________________C_o_n_t_a_c_t__________________ |
| 40 |
|
| 41 |
Mail: wrobel@g.o |
| 42 |
WWW: http://www.gunnarwrobel.de |
| 43 |
IRC: #gentoo-web at freenode.org |
| 44 |
_________________________________________________ |
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-web-user@g.o mailing list |
Archives