Re: A virtual file system

Quoting Martin Jansen <mj@php.net>: > I suggest to create a "usual" package.xml like you would do it for > every package maintained in PEAR's CVS. After having created the > tarball via "pear package", you have to options: Got it. Yes, this is what I was after. I have a question about the package.xml format, though. Right now I have this for the filelist: <filelist> <dir name="/"> <file role="php" baseinstalldir="/">VFS.php</file> <dir name="." baseinstalldir="VFS"> <file role="php">file.php</file> <file role="php">ftp.php</file> <file role="php">musql.php</file> <file role="php">sql.php</file> <file role="php">sql_file.php</file> </dir> </dir> </filelist> ... and I'm building the package in horde/lib/VFS/, which is the natural place for the package.xml to live. This works only if I copy VFS.php (which lives in horde/lib/) into horde/lib/VFS/, which is a little awkward. Is there any way that I can tell package.xml to pull the VFS.php file from the parent directory, without screwing up where it gets installed (which using ../VFS.php to reference it does)? Thanks, -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