Re: Request Tracker's Massive Dependencies -- RPM-ified?
"Nicolas Mailhot" <[email protected]>
| Newsgroups | gmane.linux.freshrpms.user |
|---|---|
| Message-ID | <[email protected]> |
On Mar 16 août 2005 02:23, Steve Bonds wrote: > FreshRPMs Folks: > > I'm about to embark on building RPMs for all of RequestTracker's > horrible dependencies, and if things go well, for RequestTracker > itself. Has anyone else already done (or attempted) this? RT3 is currently being packaged in FE, so it'll probably be available for FC4+. Reviewing all the perl dependencies is a long process. A lot of people have rpm-ified RT at one time or another (me among others). The problem is not doing it but doing it cleanly and maintaining/updating the huge pile of resulting packages afterwards. Usually people do the initial packaging, and by the time they're finished they're so fed up with RT they don't take the time to clean up their packages or update them afterwards. Therefore, I seriously advice against doing it alone outside a project where you'll be able to spread the load. The most cost-effective approach right now would be to join the FE effort, help hasten the packaging/review/test process for FE devel, and then port/adapt the result to whatever RHEL/Centos/FC version you intend to use. A quick and dirty RT packaging will be quicker, but in six months you'll be banging your head against walls for not doing it properly. At least that's my experience with this process. You've been warned. Regards, -- Nicolas Mailhot