Date: Wed, 28 Feb 2024 00:52:33 +0100 From: Hubert Tournier <hubert.tournier@gmail.com> To: freebsd-ports@FreeBSD.org Subject: re: Port tree linter Message-ID: <1d9568c9-b2b6-468e-8bc5-509d9aa4ed99@gmail.com> In-Reply-To: <cb6f89d3-3f7b-4beb-bd6a-83c95faec3c3@gmail.com> References: <cb6f89d3-3f7b-4beb-bd6a-83c95faec3c3@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Le 27/02/2024 à 23:54, Chris a écrit : > On 2024-02-27 09:50, Hubert Tournier wrote: >> It's called portlint2 (https://github.com/HubTou/portlint2), and it >> checks the >> ports Index file and the port's makefiles, for the whole port tree, >> or for >> selected categories / maintainers / ports. > While I haven't (yet) tried it out. I'm grateful for your work. It'll > potentially save a > bunch of work, Thanks! There's an example of output on a whole up-to-date port tree and index there: https://www.frbsd.org/xch/stdout.txt https://www.frbsd.org/xch/stderr.txt And an example run on your own 171 ports here: https://www.frbsd.org/xch/chris.txt On a not up-to-date index, you would notice lots of non existing port-path and description-file, which is what caught my eye in the first place. That's because the portsnap method that I use to sync my port tree doesn't update the Index at all. The tool design is modular, so if additional checks are useful to someone, they could probably be added quite easily (use the GitHub page for these interactions). > Shouldn't this make it to ports-mgmt/ as portlinter? If it's deemed useful, I could make the port next week-end. Best regards, Hubert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1d9568c9-b2b6-468e-8bc5-509d9aa4ed99>