Date: Mon, 25 Oct 2004 15:30:49 -0400 From: Frank Laszlo <laszlof@vonostingroup.com> To: Kris Kennaway <kris@obsecurity.org> Cc: will@freeBSD.org Subject: Re: [ports-i386@FreeBSD.org: rlwrap-0.18 failed on i386 4] Message-ID: <417D5469.9070807@vonostingroup.com> In-Reply-To: <20041025192727.GA63250@xor.obsecurity.org> References: <20041023224654.GB4363@xor.obsecurity.org> <417CF8A9.9090003@vonostingroup.com> <20041025192727.GA63250@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote:
>On Mon, Oct 25, 2004 at 08:59:21AM -0400, Frank Laszlo wrote:
>
>
>>I did a sweet of INDEX to check for other ports depending on
>>devel/readline, I didnt come up with anything other than my own
>>'ftp/quftp' port. Is this a new port? Or maybe I just missed it.
>>
>>
>
>It's been there for 3 years, so no :)
>
>In general you have to do a grep -r instead of just checking INDEX,
>because not everything depends on a given port by default - the
>dependency might be hidden behind an option. In this case, it's only
>a dependency on 4.x systems since 5.x includes a newer version of
>libreadline that satisfies the dependency requirements.
>
>
>
>>which needs to be upped to libreadline.so.5, I have submited a PR to fix
>>this and CC'd the original port submiter (ijliao) The maintainer appears
>>to be ports@. Maybe I should assume maintainership for this port? Thanks
>>for the heads up Kris.
>>
>>
>
>Thanks, we can always use more maintainers :)
>
>Kris
>
>
Should I submit a PR w/ patch for the MAINTAINER change? or can you hack
this in? Thanks
Regards,
Frank
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?417D5469.9070807>