You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rivet-dev@tcl.apache.org by Harald Oehlmann <Ha...@Elmicron.de> on 2010/05/12 11:36:14 UTC
Rivet rpm questions
Hello List,
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"
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.
Regards,
Harald
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Rivet rpm questions
Posted by Reinhard Max <ma...@suse.de>.
On Wed, 12 May 2010 at 17:53, David Welton wrote:
> [...] but having one spec file sounds like a good thing to me - is
> that something we could keep in subversion?
yes, of course.
You can even ship it with your source releases, as rpmbuild is able to
build a binary package from a spec file that is contained within the
source tarball.
OTOH, I wouldn't consider an included spec file as more than an
example or template, because it often happens that it needs some
tweaking to fix build problems on some distro/version that do not
justify releasing a new source tarball.
cu
Reinhard
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Rivet rpm questions
Posted by David Welton <da...@dedasys.com>.
> Aim would be:
> - have one spec-file for all platforms
>
> I am new in Rivet and rpm, only asked about "does not build on SuSE", I
> am not the best person for that. I know TCL and Unix.
I am not very knowledgeable about the world of RPM, but having one
spec file sounds like a good thing to me - is that something we could
keep in subversion?
--
David N. Welton
http://www.welton.it/davidw/
http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Rivet rpm questions
Posted by Harald Oehlmann <Ha...@Elmicron.de>.
> 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/
Jeff,
thank you, very helpful.
SuSE is slightly different how the module is loaded.
But nevertheless I got maintainer for:
https://build.opensuse.org/package/show?package=apache2-mod_rivet&project=Apache%3AModules
where many platforms are included:
CentOS, Fedora, RHEL, SLES, OpenSuSE
With the current spec-file, only SLE11 and all OpenSuSE Versions build.
People may look to the error messages for the other platforms, they are
mostly in the lib step of make.
How to proceed:
- you get maintainer at the SuSE build farm and I get out (my prefered)
- We stay as we are and keep good syncronisation.
Aim would be:
- have one spec-file for all platforms
I am new in Rivet and rpm, only asked about "does not build on SuSE", I
am not the best person for that. I know TCL and Unix.
Anyway, back on friday, tomorow holiday in germany.
Regards,
Harald
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Rivet rpm questions
Posted by Jeff Lawson <je...@bovine.net>.
On Wed, May 12, 2010 at 5:58 AM, David Welton <da...@dedasys.com> 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: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Rivet rpm questions
Posted by David Welton <da...@dedasys.com>.
> 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?
--
David N. Welton
http://www.welton.it/davidw/
http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org