On Sun, 23 Feb 2025 01:30:54 +0100 Piotr Smyrak <ps.po...@smyrak.com> wrote:
> On Sat, 22 Feb 2025 15:09:08 +0000 > Paco Pascal <m...@pacopascal.com> wrote: > > > I am writing a port for gf2. The developer of gf2 is inconsistent > > with the name, switching between "gf" and "gf2". Because of this, I > > wasn't sure what to name the port and almost sent a patch with the > > wrong PORTNAME. It might be handy to have portlint spit out a warning > > to catch when the PORTNAME doesn't match its path. For example, > > > > $ cd devel/gf2 > > $ portlint -a -A -m -N -c -C > > looks fine. > > $ grep PORTNAME Makefile > > PORTNAME= foobar > > This is somewhat more complex than your example. Ie. Python ports have > py-foo naming convention in the ports tree, while their packages are > prefixed with py311-foo, py38-foo, etc. > > -- > Piotr Smyrak So as (at least some of) ports runs on Linuxulator. For example, x11/linux-nvidia-libs has PORTNAME= nvidia-libs and PKGNAMEPREFIX= linux- in its Makefile. -- Tomoaki AOKI <junch...@dec.sakura.ne.jp>
