[bt-devel] rpm questions
Martin Gruner
bt-devel@crosswire.org
Tue, 28 May 2002 16:27:04 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'd also like to welcome Lamar very much here. We really appreciate your help
a lot!
I want to put 2 issues for discussion:
1) I suggest that we stop compiling in sword and instead start to require the
official sword rpm. This will avoid file conflicts in future and simplify our
package.
2) We should reconsider the way bibletime-doc is handled. ATM it contains all
translatable files, which includes program messages, tips and doc files
including the helpdialog pages. As sven correctly pointed out on #sword,
users who don't have bibletime-doc installed (est. 60% atm, judging from the
downloads) will see 2 empty screens on the first startup (no helpdialog pages
installed). This should not be. The main advantage for doing this was that it
helps us with the translations, since the bibletime-doc package can be
re-released independantly when a new translation was finished. The main
backdraft atm is that the whole package will be re-released, not only the
additional files.
I therefore suggest the following:
- -abandon bibletime-doc
- -keep all english data in bibletime
- -introduce localized packages such as
bibletime-i18n-de
which contain all localized data for de, such as program messages, tips and
help files.
This will involve some script revision, but should be possible. Another issue
is that the admin/ dir would be in each cvs module, which is pretty much (1MB
each). We could also try to introduce a bibletime-common folder, which holds
the admin/ dir and possibly other common files as well.
Please comment on my suggestions. My solution would involve having quite a few
rpms (one for each language), which is a good idea imo. The independance for
the translators is necessary, otherwise we'll never have a release.
Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE885PLwyLo8U2VzYcRAurrAKCTGc4KmWjh/ldzd4n5ShPUShXqswCfVj2e
rkSFYOvXVvJWB03vdf5x3fQ=
=ly6E
-----END PGP SIGNATURE-----