[bt-devel] Fwd: bibletime

[Fred Saalbach]

Tim Brodie wrote:
> 
> Hi Martin:
> 
> ----- Original Message -----
> From: "Martin Gruner" <mg.pub@gmx.net>
> Subject: Re: [bt-devel] Fwd: bibletime
> 
> > > Just tell me were to put them? The only reason I've been puting them
> there
> > > already is because there have been bug fixes and they actually work
> better
> > > than the beta.
> >
> > I created a release "development snapshots" in the "bibletime for kde2"
> > package. The development versions should go there. Users who are not
> willing
> > to take the disadvantages of the development versions can use the main
> > releases. That's why they should be separated.
> 
> great!
> 
> > Btw, should we provide sword rpm's? If somebody can use a sword rpm on his
> > computer (dependent on the architecture) he can also use the bibletime rpm
> > which has sword compiled in statically.
> > IMO we should only provide bibletime rpms, and source packages (and source
> > rpms) of bibletime and sword for those who need to build themselves. That
> may
> > result in less confusion for not so experienced users.
> > Or am I wrong here?
> 
> If we are dependant on a specific release level of sword, IMHO we should
> consider providing snapshots.  For example, sword is currently at 1.65, but
> we stipulate version 1.52 (I'm not sure if this matters).
> 
> I would also suggest that we should also provide a base set of modules
> (as well as any required fonts) as well with the expressly
> stated purpose to "get you up and running as quickly as possible". Perhaps
> the sword team can give us download stats to determine what should be
> in the common set?

We need to add instruction for fonts, I was waiting for the problems
with non western fonts and qt to get somewhat resolved.  It might be
that the fonts should be added to the install package, but the modules
are a bit big for the download.  We should not make it biger than
necessary. 
> 
> We then can provide them with good documentation on how to:
> i) locate/download/install/configure additional modules, and
> ii) locate/download/install/configure recommended fonts for modules in i).

I presume you are talking about adding sword modules.  Look at the
instructions in the document set in the installation section.   There
are actually a number of ways to install modules.  My instructions are
different from what Brook uses in his RPM's.  As the RPM's will not
install unless bibletime is installed as an RPM, it probably does not
matter.

Fred
> 
> This would then position us to be able to automate these tasks (ith
> dialogues in v1.1) to give the user a checklist of modules to pull
> down from the sword ftp site.

That is a really long list now. The windows version has a feature that
aids in down loading modules.  We might try somthing like that for
version 3, but I doubt that it's worth the effort just now.

> 
> If we merge a specific release of sword into bibletime by static link,
> then we can forego the sword rpm,  but I would still suggest we consider
> providing the other co-requisites to make bibletime usable from install
> time.
> 
> Regards... Tim