pfr It builds and installs. I wonder if it's possible to add the man pages though ?

I know it does but, does it run?
I have the man pages ready in a new version locally.

    pfr ok, thanks. I'll try to get it merged tonight.

    2 months later

    This is not a package thing but pkgsrc doesn't work well with Linux systems that don't use GNU coreutils (Alpine, Chimera Linux, etc). It'd be great for the commands used on Linux to be less GNU-specific in order to work with the alternatives (busybox, bsdutils, etc) without too much modifications because pkgsrc would try to build coreutils while bootstrapping almost all the time.

      imachocbar Are there still problems? I fixed a bunch of them uh... was it last year? I have no sense of time any more.

        nia maybe a wiki entry like the one Michael Forney wrote for oasis would be helpful. Unfortunately, I forgot what was oasis specific and, what would generally apply for Alipine or, other musl based platforms with non-gnu tools.

        • Jay likes this.

        chromium and then ungoogled-chromium and then brave-browser and of course vscode
        lvgl

        and create a mac-like DE (like helloSystem is doing) on top of arcan :D using lvgl as GUI toolkit

        • Jay likes this.

        nia yeah there are still a few. On Alpine it took some effort to bootstrap since pkgsrc somehow doesn't wanna use busybox's awk.
        I also have CMLFS on my other hard drive, but I have Chimera's fork of bsdutils installed instead of GNU core/diff/findutils. I had to remove the coreutils detection part in mk/tools/replace.mk to bootstrap. But it didn't use the installed perl, python and sed (I used NetBSD sed from nbase) and instead reinstalled them (among with a lot of stuff).

        Oasis's pkgsrc took less effort to bootstrap, but it's a bit outdated now.

          imachocbar pkgsrc somehow doesn't wanna use busybox's awk.

          For the record, I always set TOOLS_PLATFORM.{awk,sed,install} to nbawk, nbsed [1] and bsdinstall respectively on systems different from NetBSD, because otherwise the install target of some of the packages I typically build (I lost track of which), would fail (even by using gawk, gsed, and what else). I don't know it that's still the case. SmartOS still uses these settings by default.

          [1] It has to be noticed, however, that the standalone nbsed package is outdated compared to the sed version found in base NetBSD.

            JuvenalUrbino I had to put them into mk.conf while the bootstrap script was building libarchive, otherwise it'd try to install nawk after it and get into a "dependency circle" with cwrappers, or whatever it's called.

            Also @nia the tnftp and tnftpd bundled with pkgsrc are outdated for about 7 years now, I think they also need to be updated.

            13 days later

            Been AFK for a lot time this summer/fall, but I eventually managed to make up my mind about packaging Plan9 From User Space, so I updated and revised the already existing wip port (by @leot), imported as wip/plan9port. Currently it builds fine on a pkg_comp sandbox on amd64.
            Since plan9port is historically a tricky package for *BSD, additional testing is highly appreciated 🙂. @trinity @yeti @pfr

            3 months later

            I would love to see the programming language Crystal ported to NetBSD. I have found an abandoned WIP port from 2020. The Crystal compiler uses an LLVM backend, so I imagine it would not be the easiest port to maintain. Apache 2.0 license.

            Other than that:

            • fcron -- cron with more sophisticated scheduling. Tested by the developer on NetBSD 2.0. GPL v2.
            • nq -- a daemonless command line job queue. Tested by the developer on NetBSD 7.0.2. Public domain.
              14 days later

              pin

              I have not. I just recently learned about navidrome. It's available for many OS's, including FreeBSD. If the binary was available in pkgsrc it would make things easier on netbsd obviously.

              • pin replied to this.

                nortonham If the binary was available in pkgsrc it would make things easier on netbsd obviously.

                I understand that but, let's twist that a bit shall we?

                If you could say it works when built from source, it wouldn't be a waste of time for any of us to try to package it 😉