Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Oct 2020 04:21:15 +0100
From:      tech-lists <tech-lists@zyxst.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: usr/ports make readmes & description
Message-ID:  <20201002032115.GA3769@rpi4.zyxst.net>
In-Reply-To: <20200930142901.10e1bab2.freebsd@edvax.de>
References:  <20200930005948.GA82633@bastion.zyxst.net> <20200930142901.10e1bab2.freebsd@edvax.de>

next in thread | previous in thread | raw e-mail | index | archive | help

--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 comforta=
bly 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} "=3D=3D=3D>   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?
--=20
J.

--azLHFNyN32YCQGCU
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl92nKEACgkQs8o7QhFz
NAV6/BAAlvVGTxgu56u0RKHKsTr5IobqgttyX2lqJKcJfdCs4caejDoXUiX7Eoec
CsAjSGOHmZO8FVlYAvNpq2Y6O88cR8XLvzSbgG4/C04qdfdfDiAuewZbEma6gVtH
YrdlfmTxqMfMBvcxzYe5LvIr2jANmKLoOur9VlR4kfLzgp/j3BJjB+t3IblzWuq+
MU1Cpkwy31jOrM1HJP0UoW+S58zKDhpi+w4kTmsQPfWFNQ9nh4peUfUsGcDxlTDu
sGMD1yWEa9fSDD97oQeMvc6E0RxYBYQTWezt/dt+ni2uwTBC8oG7rNlAH+/p6GsX
WMtlj3Qca+9PORV4ceZ3jxzj5g+QwA+nvnLHcca6+zksBYXvs3U9s23wx/YlFQ+e
1uRlyeYPCqQAdJ6/vK0TtsBU9y0VmeVcWpm5iwPeCZ05vzjmQECQxC/sCSJO+Xah
nY3dtDhizkha8T9b9rRzpG6GgaS0fI6qcavifCMsfACr2xPJRTcZ5s/XV66AjnRS
S4x7yr3QPqigME6ZpPY4AyLjuCvQ9qDSpihYbrp8JEieJL+qP2MrydLY2oIztiub
kRwx9rB25zKW61SsLAaudR/5OIw+eqwZv3AGI8KfANr/BsayRII3i0h8p/SNA0sq
XsXmM/QCh/BhLTP4NYbRCypnfsctDDHvS1Hc2zcI/KEfZLFLsbc=
=6tFE
-----END PGP SIGNATURE-----

--azLHFNyN32YCQGCU--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201002032115.GA3769>