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

[Dan Langille]

On 11 Apr 2005 at 14:49, Gavin Atkinson wrote:

> On Mon, 2005-04-11 at 08:29 -0400, 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 :)
> > > 
> > 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 would actually like it to email the maintainer (possibly as well as
> the committer) if the maintainer has registered with FreshPorts - is
> that possible?  

The maintainer could be easily added.

> If not, making the failures public would make sense.

Breakages become public later anyways... when INDEX breaks.  Sanity 
Tests are advance notice of that.
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/
   NEW brochure available at http://www.bsdcan.org/2005/advocacy/