Date: Sat, 1 Apr 2000 19:06:07 -0800 From: "Jay Krell" <jay.krell@cornell.edu> To: <lioux@uol.com.br>, <ade@FreeBSD.ORG> Cc: <freebsd-ports@FreeBSD.ORG> Subject: Re: ports/15481: ports/devel/codecrusader slightly broken Message-ID: <006b01bf9c50$6715c560$0201a8c0@jayk_home4nt>
next in thread | raw e-mail | index | archive | help
>> 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.
I know, but that's all I could figure out so far.
>> Finally, looking at the build logs from bento, it would
>> appear that this port is broken in a number of other ways, too.
Yep, I just tried again and it was more/differently broken, an error in ACE
about a function call mixing int* and u_int*..
>However, I'd rather send
>in full patches later on and take over if its okay with the maintainer.
The patches should probably be sent to the original author besides just the
port maintainer. That should probably be the case for all ports in case it's
a real bug or the author is willing to maintain an #ifdef __FreeBSD__ or
#ifdef __BSD__ or #ifdef __unix__ or whatever the case may be..
- Jay
-----Original Message-----
From: lioux@uol.com.br <lioux@uol.com.br>
To: ade@FreeBSD.ORG <ade@FreeBSD.ORG>
Cc: jay.krell@cornell.edu <jay.krell@cornell.edu>; freebsd-ports@FreeBSD.ORG
<freebsd-ports@FreeBSD.ORG>
Date: Wednesday, March 29, 2000 8:41 PM
Subject: Re: ports/15481: ports/devel/codecrusader slightly broken
>> 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 either 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 and take over if its okay with the maintainer.
>
> 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?006b01bf9c50$6715c560$0201a8c0>