Re: A virtual file system

Quoting Jon Parise <jon@php.net>: > I'm largely indifferent. On one hand, it's a fairly generic component > that will no doubt be useful to others. On the other hand, a bunch of > the Horde components are starting to rely on these Horde libraries, > and adding the code to PEAR would no doubt create something of a fork. > > Our users have all sorts of trouble getting PEAR components running > (we require the Log package, for instance), and this would just > introduce another dependency for them to tackle[1]. This sums up my feelings, too. I have a suggestion, though: PEAR is supposed to allow distribution of code that isn't actually in the PEAR CVS repository. Why don't we add a package.xml to Horde's CVS and generate a tarball that will allow anyone to install just the VFS libraries as a PEAR component. Anyone in the PEAR community who wants to work on the code itself is welcome to get a Horde CVS account or to just send us patches. Any reliance on the Horde libraries in the code can either be refactored out, or wrapped in a small Horde-base PEAR package that would be a dependancy. We could use this as a test case for releasing other Horde components this way, too. That way development takes place in only one place, there is no fork, the entire PEAR community gets an easily installable package, and Horde users don't get an additional external dependancy. -chuck -- Charles Hagenbuch, <chuck@horde.org> "After a few minutes the most aromatic and nice smelling Italian coffee will come out of the exhaustpipe." - Our stove-top espresso pot