Date: Thu, 08 May 2008 10:36:07 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: Alfred Perlstein <alfred@freebsd.org> Cc: Peter Jeremy <peterjeremy@optushome.com.au>, src-committers@freebsd.org, cvs-all@freebsd.org, John Baldwin <jhb@freebsd.org>, cvs-src@freebsd.org Subject: Re: cvs commit: src/include stdio.h src/lib/libc/stdio clrerr.c feof.c ferror.c fileno.c getc.c getchar.c local.h putc.c putchar.c xprintf.c Message-ID: <4822BB77.6060601@FreeBSD.org> In-Reply-To: <20080508005653.GH32532@elvis.mu.org> References: <200805051603.m45G3rrN089219@repoman.freebsd.org> <200805051637.43073.jhb@freebsd.org> <20080507064013.GU32532@elvis.mu.org> <200805071111.39938.jhb@freebsd.org> <20080507231444.GF32532@elvis.mu.org> <48223918.4010001@FreeBSD.org> <20080508005653.GH32532@elvis.mu.org>
index | next in thread | previous in thread | raw e-mail
Alfred Perlstein wrote: > * Kris Kennaway <kris@FreeBSD.org> [080507 16:20] wrote: >> Alfred Perlstein wrote: >>> (*) Important note: when considering autoconf scripts, most of the >>> scripts test's come from a repository of scripts or are carbon >>> copied from each other. Saying that "all ports are broken" is not >>> true, it is a single suite of configuration scripts that are broken >>> and need fixing, then we will be OK. >>> >>> We have precident here of hacked autoconf and ports build logic >>> that automatically "seds" various things in scripts. I think >>> a few knobs can fix this for us. >> The offer was a serious one. If you're interested in evaluating the >> impact of this change on ports then just say the word. > > There's no way I can look at this within the next two months. > > Afterwards I will give it a shot if time permits. No problem, send portmgr an email when you're ready. Of course, if someone else wants to look at it before then, that's fine too. Krishome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4822BB77.6060601>