Re: [OVC-demo-team] BRP code/documentation update

From: Eron Lloyd <elloyd_at_lancaster_dot_lib_dot_pa_dot_us>
Date: Mon Mar 22 2004 - 17:15:46 CST

On Saturday 20 March 2004 12:31 pm, David Mertz wrote:
> > This would probably be a good time to
> > discuss packaging/installation of everything together. Should each
> > piece be a
> > separate package, or should we keep everything together?
> I'll defer to Fred on this. But my own opinion is that the whole
> EVM2003 package is not particularly large, so we might as well just
> require users to grab the whole thing. Well, actually, I guess the
> sound files *are* large, maybe those should be packaged separately.
> Also those are both language and nationally specific--e.g. I don't
> think an Aussie who downloads our package wants to demonstrate Alan's
> California accent, even though both speaking English (nothing against
> Alan's fine speaking voice is meant :-)).. And certainly the Spanish
> or Hindi versions will use different sound files.

True. I would be careful about trying to break everything out too much for the
first deadline (one week away!)... We can do that soon after. The thought
about sound files do make a good point. While I'm not too concerned about
localization, the sheer size of all that should be considered.

> > Do we want to set it
> > to live in <python>/site-packages? Also, how are we going to launch the
> > programs (shell, .desktop files, GUI, etc.)? If we make these
> > decisions now,
> I think $PYTHONPATH/site-packages/evm2003/... is a good place for the
> files to live. That's what distutils will give us by default. But we
> want symlinks, or shell scripts, or desktop icons, to launch the apps.
> I'm not sure about the launching part--it seems a bit platform-specific
> (should we assume *nix/KDE?).

I strongly suggest assuming our platform will be Linux/KDE-based. I will go
even farther to recommend SUSE as the distribution, citing the ease of use
and fantastic support for hardware & configuration.

Regarding launching procedures, should we create symlinks for things like my to /usr/local/bin? Personally I think that would scare people away,
and would opt more for .desktop files, which are very easy to setup.


Eron Lloyd
Technology Coordinator
Lancaster County Library
Phone: 717-239-2116
Fax: 717-394-3083
[This E-mail scanned for viruses by Declude Virus]
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
Received on Thu Apr 1 02:40:31 2004

This archive was generated by hypermail 2.1.8 : Thu Apr 01 2004 - 02:40:36 CST