Closed Bug 321835 Opened 19 years ago Closed 19 years ago

Please add a .spec file for building RPM's

Categories

(Bugzilla :: Installation & Upgrading, enhancement)

2.20
All
Linux
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: nkadel, Unassigned)

References

Details

Attachments

(2 files)

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Build Identifier: 

I've built some .spec files for building bugzilla RPM's. The latest Fedora Core 4 includes all the necessary Perl RPM's, and the optional ones, as part of the Yum or up2date available package management, so building from CPAN sources is no longer necessary and is in fact a perilous idea in a production environment where other packages may be sensitive to Perl component versions but have those packages replaced, unknown to the package management system, by doing a CPAN installation.

The .SPEC file adds a .conf file for RedHat style HTTP configurations, sets up the documentation in /usr/share/doc/bugzilla-[version], correctly sets permissions in the RedHat default directory /var/www/html/bugzilla, and lists dependencies which are easily resolved through YUM. I used to publish a set of SRPM's built up from CPAN source for this, but it's no longer necessary.

Could I poosibly submit my bugzilla.conf and bugzilla.sped files for inclusion in the "contrib" materials, to avoid exactly the work I went through to get this under RPM package management?

And by the way, whoever did the "Bundle::Bugzilla" work for CPAN is to be commended: I used that as a source of generating dependencies, since the naming of CPAN packages often has little to do with the functions they contain.

Reproducible: Always
This is the bugzilla-2.20 spec file I mentioned in my request for RPM build capability for bugzilla.
This is the HTTPD conf file I mentioned in my request for RPM support. Installing this in /etc/httpd/conf.d/ on a normal RedHat-style OS adds access to /var/www/html/bugzilla with the right permissions for Bugzilla use, rather than having to hand-edit your local httpd.conf file and possibly making mistakes that would break local security.
The .spec file I wrote is specifically for version 2.20. It can certainly be updated as appropriate.
Version: unspecified → 2.20
you already opened bug 230534 for this same request. Why opening a new bug???
Because I didn't see the old one when I looked on the site, and lost track from my work over a year ago as to whether I'd submitted it here as well as my old work Bugzilla. Mea Culps.

Let's mark the old one a duplicate. RedHat 9 required a large number of add-on RPM modules, but those are now entirely available as part of the "extra" modules. And that old website should have been flushed over a year ago when I went to a new workplace, the SRPM is out of date, etc. All we really need is the add-on .spec file and .conf file. for an RPM builder, or getting the files into the "contrib" directory or in, say, "contrib/redhat", then tweaking the .spec file to look in the right place fo the new location of the .conf file.

I'd be happy to do that.
*** Bug 230534 has been marked as a duplicate of this bug. ***
I'd rather not include a Red-Hat-specific .spec file in Bugzilla's CVS.

Instead, you should submit your RPM to Fedora Extras. I'm sure they'd be very, very happy to have it. http://fedoraproject.org/wiki/Extras

If you want to make an RHEL RPM, you should consider giving it to Dag -- http://dag.wieers.com/packages/
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
My .spec file is fairly generic, and easy to maintain: it would help me get it into the Fedora extras listings if you can include the listings in contrib. I'm also about to move out of the country, and can't easily point people to a stable website for me to support, which is a pre-requisite for the Fedora "extras". Dag might take it: I'll try that resource tomorrow.

But having a .spec file in the tarball itself is really, really useful for RPM-based distributions other than RHEL or Fedora Core. Even SuSE and Mandrake is much easier to build a clean RPM for if there's some basic one already in place to work from, and the bugzilla tree really seems to be the best place for that rather than forcing people to *ANOTHER* website, only mentioned in the bugzilla entries. The contrib directory seems like *exactly* the place for it, unless you see some real architectural reason not to have it in the source.
That does sound like a generally reasonable argument to me, but I'd still much rather have this maintained in Fedora Extras than in our contrib. I can all-too-easily see this .spec file becoming out-of-date and then becoming a pain for us in contrib/ while being updated in Fedora Extras.

If you need some web space to maintain this RPM, though, we could provide that. That would allow you to get it checked-in to Fedora Extras, and also give you complete control over the web site. If you want to do that, we can reopen this bug and move it to the "bugzilla.org" component.
Hardware: PC → All
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: