On Wed, May 12, 2010 at 5:58 AM, David Welton <[email protected]> wrote: >> as total new to Rivet, I risk to get Rivet packet maintainer for SuSE-Linux. >> >> Reinhard Max (TCL maintainer at SuSE) and me had some questions: >> >> 1) most apache modules are named as: "apache2-mod_xxx" >> >> Would it be preferable to name the module: "apache2-mod_rivet" >> instead: "rivet" > > I think most people will use it as an Apache module, so naming it that > way makes sense. > >> 2) Is it preferable to split the module and the rivet tcl tree in two >> modules ? >> >> This might be helpful, if the rivet tcl tree is of any use to an end >> user without apache. >> >> If yes, which files must go in which rpm. >> What would be the name of the rpm's. > > That sounds kind of tricky. Why not start with the simplest thing > (package it all together), and then if people request that some of the > Tcl code gets split out, worry about it then? >
Reinhard, You may also want to be aware of RPM that I have created for the RPMForge project. I'm not sure about the compatibility of RPMForge packages and SUSE/SLES, so it may not completely eliminate the need for your own version of the RPM. In any case, you may wish to use my spec file as a template for your work to ensure some consistency in packaging. http://github.com/bovine/rivet-rpm http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/mod_rivet/ Thanks Jeff --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
