[Phplib-users] Re: [Phplib-core] cvs and release stuff

[Giancarlo <gia...@na...>]

Joe Stewart wrote:
>>JS> With which directory structure?
>>I'd keep existing (php-lib) directory structure - it's much more clean
>>then in -stable (I even think that the directory structure in -stable
>>should be changed accordingly).
>>

The change in structure is only a minimal startup quirk, but  I think 
most existing user would favor the traditional simple structure, was it 
only 'cause it offers a quick upgrade path. I was surprise myself in 
seeing that many core .inc files (local4, auth4), in the php-lib 
structure, are really not needed and can be merged in a single one. Less 
maintenance.
The php-lib structure is surely more apt to develop custom or exotic 
extensions, so in the end is good. Not at the start though. Such a 
'dual' situation anyway is to be terminated ASAP, otherwise next time 
we'll have to backfix again among the two. I think as soon as the two 
cvs branches have the same structure, never mind which, the better. I 
wouldn't delay the riunification.

Gian

PS
Why not keep the new, but move what included by the prepend.php3/4 in 
the main (php) dir, and leave the subdirs for contribs and development? 
So one can have a 'compat' single php tree that works with old prepend, 
and go and search for fancy extra modules in the subdirs?  If he so 
skilled as to need them, he can bear the extra effort. This could be a 
third way: the 3 session*.inc, user*.inc and auth.inc are back to php 
dir, development, exotic and contributed extras are in their respective 
dirs. But never mind, for me anything it's ok, but I wouldn't delay an 
unique structure.