This is a great idea. I definitely think we should do this. Are there any other things that would be useful.
Daniel On 11 Feb 2002 at 23:21, David White sent forth the message: > On Mon, 2002-02-11 at 23:00, Daniel Glassey wrote: > > > > Good idea, just need to decide where to put the files. I assume /usr/share/sword >is > > the right place since that fits the FHS? > > It also needs work on the website jsp that puts the modules together. > > I would suggest that when sword is installed, it installs a script into, > perhaps /usr/bin, called sword-config. This would be able to be queried > by other programs for sword configuration information. > > For example, > > sword-config --modules-path > > would print out the path to modules. That way the Makefile can simply > have the command > > cp * `sword-config --modules-path` > > if sword-config is not present, it can also print a message saying that > Sword doesn't seem to be installed. Further, compilation of frontends, > such as BibleTime can use this script, using a different extension, such > as: > > sword-config --libs > > would expand to -lsword (and whatever other libs sword might need). > Likewise, > > sword-config --include > > would expand to -I/path/to/sword/include > > You might already have a better system in place, but this would be my > suggestion. Gtk+ uses a system much like this. > > > > > > - It would also be good to have RPMs, as this is a widely used format > > > under Linux. > > > > again that's a good idea. I've written scripts that automatically create DEBs for >all the > > modules, but I don't know anything about how to do that for RPMs. > > Yeah, I don't know anything about RPMs either. I just know that *lots* > of Linux users love them, and if users love them, then they are A Good > Thing to have. I know lots of people who don't even get software if it's > not available as an RPM. > > God Bless, > > David. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
