Date: Thu, 30 Mar 2000 01:23:29 -0300 From: lioux@uol.com.br To: ade@FreeBSD.ORG Cc: jay.krell@cornell.edu, freebsd-ports@FreeBSD.ORG Subject: Re: ports/15481: ports/devel/codecrusader slightly broken Message-ID: <20000330012329.B77600@Fedaykin.here> In-Reply-To: <200003292228.OAA63551@freefall.freebsd.org>; from ade@FreeBSD.ORG on Wed, Mar 29, 2000 at 02:28:46PM -0800 References: <200003292228.OAA63551@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> State-Changed-Why:
> Updates to ports should be provided in unified diff(1) format.
> Secondly, putting in symbolic links outside of the ${PREFIX},
> just to deal with (broken) code that expects a particular
> filesystem layout is bad.
> Finally, looking at the build logs from bento, it would
> appear that this port is broken in a number of other ways, too.
>
> So, unless I hear otherwise, this PR will be closed
> one month from today.
This port is very broken.
I have codecrusader working down here. However, an automated port
will require some time I won't have in the following 2 weeks.
Nevertheless, I should be issuing a port patch afterwards.
Furthermore, I would like to take over the port if my patch is
accepted since it seems as this port has been dropped or forgotten by
its maintainer. No offense meant. It is just that it has been broken for
more than 4 months if my count is right. :)
If the maintainer wants to keep it, I can send him both my
impressions and my limited work on this port. However, I'd rather send
in full patches later on.
Regards,
Mario Ferreira
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000330012329.B77600>