Bug 41701 - New port: devel/RT2
Summary: New port: devel/RT2
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: keichii
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-16 04:10 UTC by plasma
Modified: 2002-12-22 05:03 UTC (History)
0 users

See Also:


Attachments
file.shar (27.15 KB, text/plain)
2002-08-16 04:10 UTC, plasma
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description plasma 2002-08-16 04:10:04 UTC
	RT is a request tracker system written in perl

	WWW: http://bestpractical.com/rt/
Comment 1 Neil Blakey-Milner 2002-08-16 08:27:19 UTC
On Fri 2002-08-16 (11:04), plasma wrote:
> 	RT is a request tracker system written in perl
> 
> 	WWW: http://bestpractical.com/rt/

Does this work on 4.x?  Last I tried, the perl modules installed
couldn't be found because they're "shadowed" by the system perl.  I
notice you're using "/usr/local/bin/perl" in your patch - did you test
this on -CURRENT, or use perl 5.8 from ports on 4.x?

Neil
-- 
Neil Blakey-Milner
nbm@mithrandr.moria.org
Comment 2 plasma 2002-08-16 09:33:36 UTC
On Fri, Aug 16, 2002 at 09:27:19AM +0200, Neil Blakey-Milner wrote:
> On Fri 2002-08-16 (11:04), plasma wrote:
> > 	RT is a request tracker system written in perl
> > 
> > 	WWW: http://bestpractical.com/rt/
> 
> Does this work on 4.x?  Last I tried, the perl modules installed
> couldn't be found because they're "shadowed" by the system perl.  I
> notice you're using "/usr/local/bin/perl" in your patch - did you test
> this on -CURRENT, or use perl 5.8 from ports on 4.x?
> 
> Neil
> -- 
> Neil Blakey-Milner
> nbm@mithrandr.moria.org

My testing system is FreeBSD 4.6-release, and it's ok.

The port's problem is, it needs Perl 5.6.1 or greater to run.  It needs
CGI.pm-2.80 or greater, which doesn't exist in ports.  You can search 
ports/36887, which proposed a CGI-2.80.  I have a wild guess: the reason
why ports/36887 remains open is CGi-2.80 needs perl 5.6.

If you want to install this port, I recommend you run 'use.perl port'
first to make perl5.6 to be the system perl, then

  portupgrade -fv "p5-*"

to reinstall your installed perl modules from ports.  You might want to
search other perl modules manually to do so.  Don't forget mod_perl.
Then run this port using

  make -DINSTALL_NEW install clean

The reason why 'make upgrade' is default is I think it makes life eaiser
when using portupgrade to upgrade newer version of this port someday.

The '/usr/local/bin/perl' is intended for I want to make sure Perl 5.6
is really used for this port.  If -current don't have it, then I'll correct
it. (I never use -current and didn't think about it.  Sorry for that.)

I don't have machines running -current, so I cannot test this port on 
-current.  I don't have machine running postgresql, DB_TYPE=Pg is not
tested either.

I think perl 5.8 is ok with this port, because I was told all RT's developers
use Perl 5.8. :)

I'm planing to make a RT-devel port, but there are some issues need to be
done first.  I'll wait one week or two to see if those issues could be 
resolved.  As I just said, RT's developers use Perl 5.8, and there might be
something to break the code if using Perl 5.6.1.


Regards,
plasma
Comment 3 Neil Blakey-Milner 2002-08-16 09:49:46 UTC
On Fri 2002-08-16 (16:33), plasma wrote:
> My testing system is FreeBSD 4.6-release, and it's ok.
> 
> The port's problem is, it needs Perl 5.6.1 or greater to run.  It needs
> CGI.pm-2.80 or greater, which doesn't exist in ports.  You can search 
> ports/36887, which proposed a CGI-2.80.  I have a wild guess: the reason
> why ports/36887 remains open is CGi-2.80 needs perl 5.6.

Oops, I meant perl 5.6, not 5.8.  Ok, it's what I expected.  I have RT
working with system perl with updated modules, installed with the
unshadow option to delete the system modules.  But just using perl from
ports is probably much easier and cleaner.  If noone else picks this up
soon, I'll try get around to this this weekend.

Neil
-- 
Neil Blakey-Milner
nbm@mithrandr.moria.org
Comment 4 Larry Rosenman freebsd_committer freebsd_triage 2002-08-26 21:15:18 UTC
Any problems getting this committed? 

(Waiting with baited breath) :-)

Thanks,
LER
-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Comment 5 Anton Berezin freebsd_committer freebsd_triage 2002-09-17 21:51:36 UTC
Hi,

On Fri, Aug 16, 2002 at 01:40:04AM -0700, plasma wrote:
>  On Fri, Aug 16, 2002 at 09:27:19AM +0200, Neil Blakey-Milner wrote:
>  > On Fri 2002-08-16 (11:04), plasma wrote:
>  > > 	RT is a request tracker system written in perl
>  > > 
>  > > 	WWW: http://bestpractical.com/rt/
>  > 
>  > Does this work on 4.x?  Last I tried, the perl modules installed
>  > couldn't be found because they're "shadowed" by the system perl.  I
>  > notice you're using "/usr/local/bin/perl" in your patch - did you test
>  > this on -CURRENT, or use perl 5.8 from ports on 4.x?

>  My testing system is FreeBSD 4.6-release, and it's ok.

>  The port's problem is, it needs Perl 5.6.1 or greater to run.

Are you sure about that?  Last time I installed RT (2.0.8, I believe),
it was surely possible to make it work with 5.005_03 - at least it does
so on our server.  Though I am the first to recommend people to upgrade
to 5.6.1, it would be extremely nice if your port were made to work with
the system perl.  In the vast majority of cases, it is possible;  in
fact, quite a number of existing p5 ports in the tree `convince' their
respective perl modules that running on 5.005_03 is not such a bad idea,
after all.

When doing that, keep in mind that RELENG_4 after 17th of June 2002 have
@INC order reversed, in order to pick the (newer) modules from ports
before the (older) modules from the system perl.  RELENG_4_6, including
4.6-release, are not good enough for that.

>  It needs CGI.pm-2.80 or greater, which doesn't exist in ports.  You
>  can search ports/36887, which proposed a CGI-2.80.  I have a wild
>  guess: the reason why ports/36887 remains open is CGi-2.80 needs perl
>  5.6.

Your wild guess is wrong.  :-)  There is no good reason why CGI.pm was
not updated.  It is now at 2.86.

Also, this is not good:

MD5 (rt.tar.gz) = 59179c054c0e05336f9b92fe3b031270

It virtually guarantees you to have the checksum changed from under you.
The tarballs with the actual version numbers can be found at

   http://www.fsck.com/pub/rt/release/

I think that this port should be reworked with these comments in mind.

That said, I found it is extremely nice that we *will* have a port for
RT2.  I was planning to make one myself, and I am very glad I do not
have to, now.   :-)  Thanks!

Cheers,
=Anton.
-- 
| Anton Berezin                |      FreeBSD: The power to serve |
| catpipe Systems ApS   _ _ |_ |           http://www.FreeBSD.org |
| tobez@catpipe.net    (_(_||  |                tobez@FreeBSD.org | 
| +45 7021 0050                |         Private: tobez@tobez.org |
Comment 6 keichii freebsd_committer freebsd_triage 2002-10-28 22:59:57 UTC
Responsible Changed
From-To: freebsd-ports->keichii

I will take care of this.
Comment 7 keichii freebsd_committer freebsd_triage 2002-12-22 05:02:41 UTC
State Changed
From-To: open->closed

committed thanks