cvs commit: ports/archivers/gzip Makefile ports/archivers/ucl Makefile ports/archivers/lzop Makefile ports/archivers/cabext

[Adam Weinberger]

Dan Langille wrote:
> On 11 Apr 2005 at 15:23, Ion-Mihai Tetcu wrote:
> 
> 
>>On Mon, 11 Apr 2005 08:18:16 -0400
>>"Dan Langille" <dan at langille.org> wrote:
>>
>>
>>>On 11 Apr 2005 at 8:04, David E. O'Brien wrote:
>>>
>>>
>>>>obrien      2005-04-11 08:04:41 UTC
>>>>
>>>>  FreeBSD ports repository
>>>
>>>FreshPorts tells me that these ports were broken by this commit:
>>
>> [ ... ]
>>
>>Next time I won't bother to make a list then :)
>>
>>flz has fixed a few, but pav suggest that the obrien might want to
>>back-out the commit so he won't fix more of them until obrien decides.
> 
> 
> FreshPorts does a sanity check for each port in a commit.  Any 
> failures are emailed to the comitter if the comitter opts in.  To opt 
> in, register using your @FreeBSD.org email address at 
> http://www.freshports.org/
> 
> Is there any value in making sanity test failures publicly available?

I believe emphatically that the sanity tests should be non-optional. The 
FreshPorts sanity checks have never been wrong for me... I personally 
think that every FreshPorts sanity check failure should be automatically 
sent to both the committer and the ports@ mailing list. If the committer 
doesn't wish to receive those emails, he can either (a) stop making bad 
commits, or (b) add a procmail filter.

# Adam


-- 
Adam Weinberger
adamw at magnesium.net || adamw at FreeBSD.org
adamw at vectors.cx    ||   adamw at gnome.org
http://www.vectors.cx