Date: Sat, 21 Jun 2003 11:17:31 -0700 From: "Rev. Joe Doyle Ardent" <ardent@nebcorp.com> To: freebsd-questions@freebsd.org Subject: Re: Strange formatting error with pkg_info after using portupgrade Message-ID: <20030621181731.GB5086@nebcorp.com> In-Reply-To: <3EF48DAD.1040702@geminix.org> References: <20030620022316.GA52638@nebcorp.com> <3EF48DAD.1040702@geminix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 21, 2003 at 06:54:05PM +0200, Uwe Doering wrote: > > Rev. Joe Doyle Ardent wrote: > > > >please:~> pkg_info |head > >BitTorrent-3.2.1b "Peer to Peer file sharing/mirroring."Mesa-3.4.2_2 > >A graphics library similar to SGI's OpenGL > >ORBit-0.5.17 High-performance CORBA ORB with support for the C > >language > >XFree86-4.3.0,1 X11/XFree86 core distribution (complete, using > >mini/meta-po > > > > Note how Mesa's entry begins immediately after the last > >character of BitTorrent's. > > [...] > > While I actually don't know why the terminating newline is missing in > some cases I noticed that there was an MFC to RELENG_4 a couple of days > ago that makes 'pkg_info' add a newline if the comment line doesn't have > one. You may want to take a look at FreeBSD's CVS repository > (src/usr.sbin/pkg_install/info/show.c) in order to build and install a > fixed 'pkg_info'. > That did the trick; thanks! Still, why does portupgrade get rid of the newlines in the COMMENT? Has anyone else seen this behavior? -Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030621181731.GB5086>