[bt-devel] sword iso

[Lamar Owen]

On Monday 15 July 2002 04:18 pm, Troy A. Griffitts wrote:
> My first line of attack was thinking that I can get you variables set to
> each distinct path that KDE might need.  From that, we can make separate
> tar.gz files for each to go where they need.  Including the small script
> to the end of this message.  Should be easily augmented to add new paths.

Well, actually, I was considering a completely different tack.  That is:
1.)	Determine what distribution we have;
2.)	use 'rpm -Uvh' to install the appropriate bibletime RPM.

Otherwise a statically linked binary would be needed; and then we'd need one 
for KDE 3 and one for KDE2.  Possibly linked to an older glibc.

> Well, the current CD setup will install an older release of bibletime.

Yes, the positively archaic 0.24, IIRC.  That's how I got my first exposure to 
BibleTime -- and the current version is not just head and shoulders above it, 
but waist, trunk, and thighs.

> Our next CD should be wrapped up sometime this week Lord willing.  If
> the bibletime setup is not updated, it will still install the older
> version of bibletime.  It's not crucial for this release, but we'd like
> to get something in place that can be easily updated with newer releases
> of BibleTime.

Yes, I understand.  My background prefers RPM format binaries; but that's not 
a showstopper if we can have enough room for binary tarballs for the target 
systems -- KDE3 versus KDE2 and the rest.

RPM's can easily be installed; not quite so easy to build, but easy to 
install.
-- 
Lamar Owen
WGCR Internet Radio
1 Peter 4:11