Re: [jokosher-devel] Managing extensions

[Luke Tilley <sinisterguy gmail com>]

I think the folder idea is a good one. Like Jens said, it keep the
extension dir clean. As for distribution however, I like the .tar.gz
idea. You could have the Extension Manager look for .tar.gz files and
then automatically untar them to the users extension dir. Another thing
we could do is distribute extensions with a file extension more
assosiated wiht jokosher, but still have it be a plain old tar.gz

As for the name conflicts. Generally, I don't think that this should be
allowed as it will confuse users, but there are also extension updates
to consider etc. I'm not quite sure what you should do for that.

-Lukas

On Mon, 2006-10-02 at 21:10 +0200, Jens Geiregat wrote:
> Or just give every extension its own folder? Keeps the extensions
> folder clean, allows extensions to have their own files, no extraction
> needed. Or force extensions to have one NAME.py file and allow a
> NAME-folder.
> 
> 
> Jens
> 
> On 10/2/06, Panos Laganakos <panos laganakos gmail com> wrote:
> > maybe install the extensions in .tar.gz archives?
> >
> > ie: cubase-exporter.tar.gz would contain:
> >
> > /
> > /ce-main.py
> > /ce-functions.py
> > /images/
> > /images/icon.png
> > /images/icon-02.png
> > /README
> >
> > If its not resource hungry to untar the extensions on loading or at
> > point of usage, I think its quite tidy that way.
> >
> > Or as you said modules or python eggs.
> >
> >
> >
> > --
> > Panos Laganakos
> > _______________________________________________
> > jokosher-devel-list mailing list
> > jokosher-devel-list gnome org
> > http://mail.gnome.org/mailman/listinfo/jokosher-devel-list
> >
> _______________________________________________
> jokosher-devel-list mailing list
> jokosher-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/jokosher-devel-list