Date: Thu, 01 Oct 2020 20:55:19 -0700 From: Carl Johnson <carlj@peak.org> To: freebsd-questions@freebsd.org Subject: Re: usr/ports make readmes & description Message-ID: <86y2kp46zc.fsf@elm.localnet> In-Reply-To: <20201002032115.GA3769@rpi4.zyxst.net> (tech-lists@zyxst.net's message of "Fri, 2 Oct 2020 04:21:15 %2B0100") References: <20200930005948.GA82633@bastion.zyxst.net> <20200930142901.10e1bab2.freebsd@edvax.de> <20201002032115.GA3769@rpi4.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
tech-lists <tech-lists@zyxst.net> writes:
> On Wed, Sep 30, 2020 at 02:29:01PM +0200, Polytropon wrote:
>>On Wed, 30 Sep 2020 01:59:48 +0100, tech-lists wrote:
>>> Years ago one could go into /usr/ports and make readmes for every single port.
>>> It'd take a while, but you'd end up with a ports tree browsable comfortably in
>>> lynx. Nowadays, make readmes only works for the top level ie /usr/ports/category and
>>> won't make the longer descriptions in HTML.
>>>
>>> How can I get the old behaviour back?
>>
>>According to "man 7 ports", this is still supported:
>>
>>readmes Create a port's README.html. This can be used from
>> /usr/ports to create a browsable web of all ports on
>> your system!
>>
>>See /usr/ports/Mk/bsd.port.subdir.mk for the target.
>
> Hi, this is my point.
>
> /usr/ports/Mk/bsd.port.subdir.mk seems to suggest that 'make readme'
> builds the category (for example cd /usr/ports/archivers && make
> readme) one gets a README.html with a one-line description of each port.
> The port name is a link but if it's selected of course it goes nowhere.
>
> Now, if instead you 'make readmes', the end result is *identical* my point
> is that make readmes used to (it was a long time ago but I'm sure of it
> now) first make the top level readme and then go into each and every
> port in that category and make the readme for all those ports. It'd take
> a long while, but what you were left with is a README.html you could
> click through right down to the port's long description.
>
> That's what it's missing. Maybe the ports tree got too big for this I
> guess? The bit in that bsd.port.subdir.mk that's not getting run appears
> to be this:
>
> [...]
> readmes: readme ${SUBDIR:S/^/_/:S/$/.readmes/}
> @${ECHO_MSG} "===> Creating README.html for all ports"
> @perl ${PORTSDIR}/Tools/make_readmes <
> ${INDEXDIR}/${INDEXFILE}
> [...]
>
> I never see "Creating README.html for all ports" regardless of whether
> i'm in /usr/ports or /usr/ports/category when I run "make readmes". Is
> this a bug?
I just did a 'make readmes' a few hours ago, and it ran without
problems, as usual. In my case I had just done a portsnap and did that
to update the README.html files. It took about 30 minutes this time
using -j4. I am running 12.1-RELEASE and just do a quarterly portsnap
to roughly match the quarterly pkg repository.
--
Carl Johnson carlj@peak.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86y2kp46zc.fsf>