Re: Structure in pear

["Martin Jansen" <mj@php.net>] > Hi, > > how do we handle the directory structure in the > pear repository? > > Example: > > We have some classes handling network related things (e.g. > Net_NNTP, Net_Ping). Should all those files have their > own top level directory or should they be moved into > a subdirectory (perhaps called "Net"), like we do > in "Science"? This question has been raised before, and the reply is that the pear CVS module directory structure is different from that install structure. The Net_NNTP and Net_Ping packages are completely unrelated, so we keep them separate to make it easier to identify packages and implement ACLs. Imagine if we had a structure like this: Net Net/NNTP.php Net/SMTP Net/Ping Upon seeing this structure, is it obvious to you what packages are represented in here? It could be one "Net" package including everything or one package for each file/directory. In practice, you would be able to see it by looking for XML package files, but that adds a lot of unnecessary complexity. So to make things simple, we say that each package has its own top-level directory in the pear CVS module. - Stig -- Stig Sæther Bakken <ssb@fast.no> Fast Search & Transfer ASA, Trondheim, Norway