on 08/12/2007 01:52 Garrett Cooper said the following:
> On Dec 7, 2007, at 8:03 AM, Stephen Montgomery-Smith wrote:
>> Here is an idea. I notice that the extra sources you want to
>> download are rather small (about 7000 bytes when zipped). How
>> about if you put the sources into the "files
On Fri, 2007-12-07 at 15:52 -0800, Garrett Cooper wrote:
> On Dec 7, 2007, at 8:03 AM, Stephen Montgomery-Smith wrote:
>
> > Andriy Gapon wrote:
> >> on 07/12/2007 15:50 Andriy Gapon said the following:
> >>> So I have this solution worth of Solomon's wisdom :-)
> >>> It is to add an option to the
On Dec 7, 2007, at 8:03 AM, Stephen Montgomery-Smith wrote:
Andriy Gapon wrote:
on 07/12/2007 15:50 Andriy Gapon said the following:
So I have this solution worth of Solomon's wisdom :-)
It is to add an option to the port, say with WITH_FUSE. When the
option
is turned on the port would down
Andriy Gapon wrote:
on 07/12/2007 15:50 Andriy Gapon said the following:
So I have this solution worth of Solomon's wisdom :-)
It is to add an option to the port, say with WITH_FUSE. When the option
is turned on the port would download my sources in addition to the
original sources, then modify
on 07/12/2007 15:50 Andriy Gapon said the following:
> So I have this solution worth of Solomon's wisdom :-)
> It is to add an option to the port, say with WITH_FUSE. When the option
> is turned on the port would download my sources in addition to the
> original sources, then modify the build scrip
There is a port, sysutils/udfclient, that I maintain.
I also have some code (written by myself) that acts as a FUSE-glue
(sysutils/fusefs-*) for udfclient, so that a UDF filesystem could be
RW-accessed via the usual filesystem means (on RW media, of course).
The thing is that the author of the ud
