Spec URL: http://www.bachelot.org/fedora/SPECS/perl-RTx-Calendar.spec SRPM URL: http://www.bachelot.org/fedora/SRPMS/perl-RTx-Calendar-0.07-1.fc10.src.rpm Description: This RT extension provides a calendar view for your tickets and your reminders so you see when is your next due ticket. You can find it in the menu Search->Calendar. There's a portlet to put on your home page (see Prefs/MyRT.html). You can also enable ics (ICal) feeds for your default calendar and all your private searches in Prefs/Calendar.html. Authentication is magic number based so that you can give those feeds to other people.
build failed http://koji.fedoraproject.org/koji/taskinfo?taskID=1272093
I was building against EL-5 where the rt version is 3.6, while Fedora has 3.8, and 3.8 is changing the place where the files are installed. I think this package will need more work. Anyway, even with 3.6 the files installed under /usr/local/lib/rt3 are probably a problem and I'll need to talk with Ralf about that.
It *is* a problem. According to the file system standard, everything that comes with the distro should be in libdir; /usr/local is for software that hasn't been packaged and is locally built.
(In reply to comment #3) > It *is* a problem. According to the file system standard, everything that comes > with the distro should be in libdir; /usr/local is for software that hasn't > been packaged and is locally built. Correct. Nothing being shipped with Fedora must install anything to /usr/local. The fact, rt3 owns some (%ghost'ed) directories therein, doesn't mean vendor supplied packages may install something there. (In reply to comment #2) > Anyway, even with 3.6 the files installed under > /usr/local/lib/rt3 are probably a problem I haven't checked all details yet, but as far as I understand (so far), your package is facing a design flaw in rt3: Lack of a "system-wide plugins directory". I am not sure what to do about it. We could try to hack rt3 to add one, we could try to change rt3 to using a plugins-directory somewhere below /usr (not /usr/local), or we can try to change/configure this package such that it installs into perl's standard system search paths.
RTx-Calendar is using Module-Install-RTx (a bundled copy, this probably needs to be fixed too). Module-Install-RTx uses rt3.pm and get the install directories from there. The following layout is defined ; customdir: %{_prefix}/local/lib/rt3 custometcdir: %{_prefix}/local/etc/rt3 customhtmldir: ${customdir}/html customlexdir: ${customdir}/po customlibdir: ${customdir}/lib I believe changing this to the default rt3 dirs would do, but I'm not sure this is the proper "fix". Oh, and also, there's no Module-Install-RTx that supports the rt 3.8 plugins framework yet.
I just successfully installed this on my FC11 RT3 via the download and instructions - it was very easy and intalled without any issue. I'd submit it but I have no idea how ...
Never mind, just noticed the comments about /usr/lib and checked, sure enough, that is where it was installed.
Folks, I'm going to drop this out of the review queue. Please clear the whiteboard if the issues with this package are resolved.
any progress here if not then please close this if issue is not getting fixed.
I have a version which fixes the files in /usr/local, but now I have to properly fix, unbundled and packaged the Module::Install:RTx perl module that is included in the tarball.
New version : Spec URL: http://www.bachelot.org/fedora/SPECS/perl-RTx-Calendar.spec SRPM URL: http://www.bachelot.org/fedora/SRPMS/perl-RTx-Calendar-0.07-4.fc10.src.rpm
New version : Spec URL: http://www.bachelot.org/fedora/SPECS/perl-RTx-Calendar.spec SRPM URL: http://www.bachelot.org/fedora/SRPMS/perl-RTx-Calendar-0.07-5.fc10.src.rpm
(In reply to comment #4) > (In reply to comment #2) > > Anyway, even with 3.6 the files installed under > > /usr/local/lib/rt3 are probably a problem > I haven't checked all details yet, but as far as I understand (so far), your > package is facing a design flaw in rt3: Lack of a "system-wide plugins > directory". FYI RT 3.8.7, which is in rawhide, added a second plugin path, which can be set in either RT_Config.pm or RT_SiteConfig.pm e.g. Set($PluginPath,"/var/www/rt3/plugins"); This will then be checked for plugins if the plugin isn't found in /usr/local/lib/rt3/plugins.
Is this *still* NotReady?
(In reply to comment #14) > Is this *still* NotReady? It isn't NotReady alone, it seems to be ultimately dead... Am I right? In this case it should be FE-DEADREVIEW.
Seems there are no objections, that's why I close this bug now, adding FE-DEADREVIEW.