Date: Thu, 06 Oct 2016 11:21:56 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-doc@FreeBSD.org Subject: [Bug 209220] "Long description" link of many ports returns error Message-ID: <bug-209220-9-TTmuWvlYP3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209220-9@https.bugs.freebsd.org/bugzilla/> References: <bug-209220-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209220 Andreas Perstinger <andipersti@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andipersti@gmail.com --- Comment #12 from Andreas Perstinger <andipersti@gmail.com> --- Created attachment 175460 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175460&action=edit Fix the long description link for ports without their own pkg-descr file This bug is not related to bug#206709 because portindex only creates the html pages for the categories listings (reachable from the left sidebar). E.g. if you go to the listing for all math ports (https://www.freebsd.org/ports/math.html) and then scroll down to the fftw3-quad port, the link for the long description works (linking to the description for the "master" port fftw3). But if you use the search box you get to another page (https://www.freebsd.org/cgi/ports.cgi?query=fftw3-quad&stype=all) where the link is broken. The search results are created by /cgi/ports.cgi (https://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/htdocs/cgi/ports.cgi?view=markup). On lines 311-314 the value from the INDEX file is correctly read into $descfile but on line 344 $l (which is based on the port's path in the ports tree) is used for creating the link. In my attached patch I've also renamed a variable name ($remotePrefixCVS -> $remotePrefixRepo) and updated the associated comment. :-) -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209220-9-TTmuWvlYP3>