[tahoe-dev] help! how do I manage dependencies on JavaScript code?

[Greg Troxel]

"Zooko O'Whielacronx" <zooko at zooko.com> writes:

> On Fri, Sep 3, 2010 at 6:34 AM, Greg Troxel <gdt at ir.bbn.com> wrote:
>>
>> That is half-baked, because it only works on the pubgrid :-)
>
> I have a vague notion that someone could run an "installer" which
> installs the JS app onto their grid instead of onto their local hard
> drive. :-)

It might as well just put it in /usr/pkg/share/tahoe-lafs/javascript/foo.js.

>> It's normal in software for all sorts of programs ('packages' in linux
>> and bsd) to depend on each other.  So are there already packages for the
>> things we want to depend on?
>
> Not the JavaScript things. I think the concept of packaging has not
> yet taken hold in the JavaScript world.

That's too bad; that's a disease of people thinking that what they do is
the main thing and it's ok for people to have to expend effort on it.
Obviously if it were that way for all 769 packages installed on my box
nothing would ever get done.


I'll also second Randy's notion that dependencies are bad, especially on
large things.  I'm all for visualization, but I'd like to see the core
tahoe-lafs be able to write files that have a machine-parseable trace,
and then a separate package to look at them, so that a working
filesystem install isn't burdened with javascript etc.

I realize there's a tension between the unix and windows concepts of
usability.  Obviously i'm coming from the unix side.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100903/c25dcd66/attachment.pgp>