Re: A virtual file system
| From: | Martin Jansen | Date: | Tue, 24 Sep 2002 19:49:09 +0000 |
| Subject: | Re: A virtual file system | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-9446@lists.php.net to get a copy of this message | ||
On Tue Sep 24, 2002 at 03:0231PM -0400, Chuck Hagenbuch wrote:
> 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)?
I haven't tried this so far, but the only solution that comes to my
mind is to use ../VFS.php. Perhaps someone else has an idea?
--
- Martin Martin Jansen
http://martinjansen.com/