Date: Wed, 6 Nov 2002 19:11:33 -0800 From: Adam Weinberger <adamw@FreeBSD.org> To: Eric Melville <eric@FreeBSD.org> Cc: Kris Kennaway <kris@obsecurity.org>, Kris Kennaway <kris@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/textproc Makefile Message-ID: <20021107031133.GB197@vectors.cx> In-Reply-To: <20021106190506.B72056@FreeBSD.org> References: <200211062255.gA6MtPuQ031772@repoman.freebsd.org> <20021106230310.GP197@vectors.cx> <20021106231336.GA17722@rot13.obsecurity.org> <20021106231718.GR197@vectors.cx> <20021106190506.B72056@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> (11.06.2002 @ 1905 PST): Eric Melville said, in 0.5K: << > > > See the email I just sent to ports@. It looks like there's a quoting > > > bug in bsd.port.mk (it is causing INDEX builds to fail when > > > PORTCOMMENT contain metacharacters). Quoting the metacharacters stops > > > the INDEX build breaking, but they show up quoted in INDEX because > > > that instance of PORTCOMMENT is correctly quoted in bsd.port.mk. > > > > Does this need to be backed out? > > The problem should only show up in comments that contain a ' character, or > perhaps characters that I haven't actually seen in any existing comments. > >> end of "Re: cvs commit: ports/textproc Makefile" from Eric Melville << Anything that has an apostraphe b0rks, and 2 plus signs. 1 plus sign is OK though. I'm about to back some of them out. - -Adam - -- Adam Weinberger adam@vectors.cx adamw@FreeBSD.ORG -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE9ydnlo8KM2ULHQ/0RAmliAKC+hLsJ58quCCARYXr08iItTfeZbwCg3F/r c/f6OBx2ohuiW4CbHiZ6WZk= =eTJd -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021107031133.GB197>