home.social

#pkgsrc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pkgsrc, aggregated by home.social.

  1. Mid May #NetBSD #pkgsrc 2026Q1 binary package counts:

    * pkgsrc-2026Q1 *

    10.0: earmv4 10849 (still needs to be fixed)
    10.0: m68k 8339 (+286)
    10.0: powerpc 24180 (+3541)
    10.0: sparc64 14530 (+509)
    10.0: vax 8731 (+1485)

    11.0: aarch64eb 23538 (+530)
    11.0: earmv4 3763 (+437)
    11.0: m68k 7979 (+873)
    11.0: mips64eb 2626 (needs to be fixed)
    11.0: mipsel 1590 (+893)
    11.0: powerpc 17208 (+9958)
    11.0: riscv64 19327 (+1596)
    11.0: vax 7002 (+668)
  2. Mid May #NetBSD #pkgsrc 2026Q1 binary package counts:

    * pkgsrc-2026Q1 *

    10.0: earmv4 10849 (still needs to be fixed)
    10.0: m68k 8339 (+286)
    10.0: powerpc 24180 (+3541)
    10.0: sparc64 14530 (+509)
    10.0: vax 8731 (+1485)

    11.0: aarch64eb 23538 (+530)
    11.0: earmv4 3763 (+437)
    11.0: m68k 7979 (+873)
    11.0: mips64eb 2626 (needs to be fixed)
    11.0: mipsel 1590 (+893)
    11.0: powerpc 17208 (+9958)
    11.0: riscv64 19327 (+1596)
    11.0: vax 7002 (+668)
  3. Mid May #NetBSD #pkgsrc 2026Q1 binary package counts:

    * pkgsrc-2026Q1 *

    10.0: earmv4 10849 (still needs to be fixed)
    10.0: m68k 8339 (+286)
    10.0: powerpc 24180 (+3541)
    10.0: sparc64 14530 (+509)
    10.0: vax 8731 (+1485)

    11.0: aarch64eb 23538 (+530)
    11.0: earmv4 3763 (+437)
    11.0: m68k 7979 (+873)
    11.0: mips64eb 2626 (needs to be fixed)
    11.0: mipsel 1590 (+893)
    11.0: powerpc 17208 (+9958)
    11.0: riscv64 19327 (+1596)
    11.0: vax 7002 (+668)
  4. Mid May #NetBSD #pkgsrc 2026Q1 binary package counts:

    * pkgsrc-2026Q1 *

    10.0: earmv4 10849 (still needs to be fixed)
    10.0: m68k 8339 (+286)
    10.0: powerpc 24180 (+3541)
    10.0: sparc64 14530 (+509)
    10.0: vax 8731 (+1485)

    11.0: aarch64eb 23538 (+530)
    11.0: earmv4 3763 (+437)
    11.0: m68k 7979 (+873)
    11.0: mips64eb 2626 (needs to be fixed)
    11.0: mipsel 1590 (+893)
    11.0: powerpc 17208 (+9958)
    11.0: riscv64 19327 (+1596)
    11.0: vax 7002 (+668)
  5. Mid May #NetBSD #pkgsrc 2026Q1 binary package counts:

    * pkgsrc-2026Q1 *

    10.0: earmv4 10849 (still needs to be fixed)
    10.0: m68k 8339 (+286)
    10.0: powerpc 24180 (+3541)
    10.0: sparc64 14530 (+509)
    10.0: vax 8731 (+1485)

    11.0: aarch64eb 23538 (+530)
    11.0: earmv4 3763 (+437)
    11.0: m68k 7979 (+873)
    11.0: mips64eb 2626 (needs to be fixed)
    11.0: mipsel 1590 (+893)
    11.0: powerpc 17208 (+9958)
    11.0: riscv64 19327 (+1596)
    11.0: vax 7002 (+668)
  6. First SmartOS pkgsrc build using GCC 15.2.0. As expected, plenty of fallout due to the ongoing strictness changes in upstream GCC.

    reports.pkgci.org/SmartOS/upst

    Hopeful that there are only a few high-profile blockers, and that the gmake failure is not more systemic gnulib-type issues where all individual releases bundle their own broken copies.

    #pkgsrc #illumos

  7. First SmartOS pkgsrc build using GCC 15.2.0. As expected, plenty of fallout due to the ongoing strictness changes in upstream GCC.

    reports.pkgci.org/SmartOS/upst

    Hopeful that there are only a few high-profile blockers, and that the gmake failure is not more systemic gnulib-type issues where all individual releases bundle their own broken copies.

    #pkgsrc #illumos

  8. First SmartOS pkgsrc build using GCC 15.2.0. As expected, plenty of fallout due to the ongoing strictness changes in upstream GCC.

    reports.pkgci.org/SmartOS/upst

    Hopeful that there are only a few high-profile blockers, and that the gmake failure is not more systemic gnulib-type issues where all individual releases bundle their own broken copies.

    #pkgsrc #illumos

  9. First SmartOS pkgsrc build using GCC 15.2.0. As expected, plenty of fallout due to the ongoing strictness changes in upstream GCC.

    reports.pkgci.org/SmartOS/upst

    Hopeful that there are only a few high-profile blockers, and that the gmake failure is not more systemic gnulib-type issues where all individual releases bundle their own broken copies.

    #pkgsrc #illumos

  10. First SmartOS pkgsrc build using GCC 15.2.0. As expected, plenty of fallout due to the ongoing strictness changes in upstream GCC.

    reports.pkgci.org/SmartOS/upst

    Hopeful that there are only a few high-profile blockers, and that the gmake failure is not more systemic gnulib-type issues where all individual releases bundle their own broken copies.

    #pkgsrc #illumos

  11. @veer66 #pkgsrc works on a number of different operating systems, including Linux and MacOS. You don't have to run #NetBSD to use pkgsrc 🤘

  12. @veer66 #pkgsrc works on a number of different operating systems, including Linux and MacOS. You don't have to run #NetBSD to use pkgsrc 🤘

  13. @veer66 #pkgsrc works on a number of different operating systems, including Linux and MacOS. You don't have to run #NetBSD to use pkgsrc 🤘

  14. @veer66 #pkgsrc works on a number of different operating systems, including Linux and MacOS. You don't have to run #NetBSD to use pkgsrc 🤘

  15. @veer66 #pkgsrc works on a number of different operating systems, including Linux and MacOS. You don't have to run #NetBSD to use pkgsrc 🤘

  16. "
    Recursion Test--Tower of Hanoi 1 2 3
    awk: log result out of range
    input record number 3, file
    source line number 11
    "
    #Fail
    The classic "BYTE Benchmark" from the 1990s, still out there in #PkgSrc

  17. "
    Recursion Test--Tower of Hanoi 1 2 3
    awk: log result out of range
    input record number 3, file
    source line number 11
    "
    #Fail
    The classic "BYTE Benchmark" from the 1990s, still out there in #PkgSrc

  18. "
    Recursion Test--Tower of Hanoi 1 2 3
    awk: log result out of range
    input record number 3, file
    source line number 11
    "
    #Fail
    The classic "BYTE Benchmark" from the 1990s, still out there in #PkgSrc

  19. "
    Recursion Test--Tower of Hanoi 1 2 3
    awk: log result out of range
    input record number 3, file
    source line number 11
    "
    #Fail
    The classic "BYTE Benchmark" from the 1990s, still out there in #PkgSrc

  20. "
    Recursion Test--Tower of Hanoi 1 2 3
    awk: log result out of range
    input record number 3, file
    source line number 11
    "
    #Fail
    The classic "BYTE Benchmark" from the 1990s, still out there in #PkgSrc

  21. @veer66 Why not create your own pkgsrc entry (ie directory, Makefile, distinfo, DESCR, PLIST and any patches) for your own software? Maybe add it to #pkgsrc-wip so everyone can use it?Then you won't be breaking abstractions, and you and others can use it on other autotools-supported platforms you may not have access to (pkgsrc makes sure config.sub and config.guess are consistent everywhere)

  22. @veer66 Why not create your own pkgsrc entry (ie directory, Makefile, distinfo, DESCR, PLIST and any patches) for your own software? Maybe add it to #pkgsrc-wip so everyone can use it?Then you won't be breaking abstractions, and you and others can use it on other autotools-supported platforms you may not have access to (pkgsrc makes sure config.sub and config.guess are consistent everywhere)

  23. @veer66 Why not create your own pkgsrc entry (ie directory, Makefile, distinfo, DESCR, PLIST and any patches) for your own software? Maybe add it to #pkgsrc-wip so everyone can use it?Then you won't be breaking abstractions, and you and others can use it on other autotools-supported platforms you may not have access to (pkgsrc makes sure config.sub and config.guess are consistent everywhere)

  24. @veer66 Why not create your own pkgsrc entry (ie directory, Makefile, distinfo, DESCR, PLIST and any patches) for your own software? Maybe add it to #pkgsrc-wip so everyone can use it?Then you won't be breaking abstractions, and you and others can use it on other autotools-supported platforms you may not have access to (pkgsrc makes sure config.sub and config.guess are consistent everywhere)

  25. @veer66 Why not create your own pkgsrc entry (ie directory, Makefile, distinfo, DESCR, PLIST and any patches) for your own software? Maybe add it to #pkgsrc-wip so everyone can use it?Then you won't be breaking abstractions, and you and others can use it on other autotools-supported platforms you may not have access to (pkgsrc makes sure config.sub and config.guess are consistent everywhere)

  26. pkgsrc คือระบบสร้างแพ็กเกจและตัวจัดการแพ็กเกจ คล้ายกับ Debian APT, Homebrew และ Pacman รวมถึง FreeBSD Ports โดยแพ็กเกจต่าง ๆ จะถูกเก็บไว้ใน source tree เดียว และระบบทำงานโดยใช้ Makefile การออกแบบนี้ทำให้ผมสามารถศึกษาได้โดยไม่ต้องกระโดดไปมาระหว่างที่ต่าง ๆ และไม่ไม่ต้องเรียนรู้ภาษาในการอธิบายแพ็กเกจใหม่

    #pkgsrc #leakyabstraction

  27. pkgsrc คือระบบสร้างแพ็กเกจและตัวจัดการแพ็กเกจ คล้ายกับ Debian APT, Homebrew และ Pacman รวมถึง FreeBSD Ports โดยแพ็กเกจต่าง ๆ จะถูกเก็บไว้ใน source tree เดียว และระบบทำงานโดยใช้ Makefile การออกแบบนี้ทำให้ผมสามารถศึกษาได้โดยไม่ต้องกระโดดไปมาระหว่างที่ต่าง ๆ และไม่ไม่ต้องเรียนรู้ภาษาในการอธิบายแพ็กเกจใหม่

    #pkgsrc #leakyabstraction

  28. pkgsrc คือระบบสร้างแพ็กเกจและตัวจัดการแพ็กเกจ คล้ายกับ Debian APT, Homebrew และ Pacman รวมถึง FreeBSD Ports โดยแพ็กเกจต่าง ๆ จะถูกเก็บไว้ใน source tree เดียว และระบบทำงานโดยใช้ Makefile การออกแบบนี้ทำให้ผมสามารถศึกษาได้โดยไม่ต้องกระโดดไปมาระหว่างที่ต่าง ๆ และไม่ไม่ต้องเรียนรู้ภาษาในการอธิบายแพ็กเกจใหม่

    #pkgsrc #leakyabstraction

  29. pkgsrc คือระบบสร้างแพ็กเกจและตัวจัดการแพ็กเกจ คล้ายกับ Debian APT, Homebrew และ Pacman รวมถึง FreeBSD Ports โดยแพ็กเกจต่าง ๆ จะถูกเก็บไว้ใน source tree เดียว และระบบทำงานโดยใช้ Makefile การออกแบบนี้ทำให้ผมสามารถศึกษาได้โดยไม่ต้องกระโดดไปมาระหว่างที่ต่าง ๆ และไม่ไม่ต้องเรียนรู้ภาษาในการอธิบายแพ็กเกจใหม่

    #pkgsrc #leakyabstraction

  30. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  31. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  32. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  33. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  34. @jpmens

    In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

    pkgsrc.se/editors/neatvi

    And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

    github.com/brentr/viless

    #NetBSD #OmniOS

  35. Hello everyone, I made some updates to ManpageViewer, fixed some bugs, implemented interface improvements, now it's easier to read the manpages, and the search system has also been improved. As you can see, I also adopted another name. I also expanded the scope, with the creation of "Custom Manpages," I can add the manpages of a specific software.

    man.nergahak.co.za/

    #man #manpages #FreeBSD #MINIX #NetBSD #OpenBSD #UNIX #pkgsrc #DataBase

  36. Hello everyone, I made some updates to ManpageViewer, fixed some bugs, implemented interface improvements, now it's easier to read the manpages, and the search system has also been improved. As you can see, I also adopted another name. I also expanded the scope, with the creation of "Custom Manpages," I can add the manpages of a specific software.

    man.nergahak.co.za/

    #man #manpages #FreeBSD #MINIX #NetBSD #OpenBSD #UNIX #pkgsrc #DataBase

  37. Hello everyone, I made some updates to ManpageViewer, fixed some bugs, implemented interface improvements, now it's easier to read the manpages, and the search system has also been improved. As you can see, I also adopted another name. I also expanded the scope, with the creation of "Custom Manpages," I can add the manpages of a specific software.

    man.nergahak.co.za/

    #man #manpages #FreeBSD #MINIX #NetBSD #OpenBSD #UNIX #pkgsrc #DataBase

  38. Hello everyone, I made some updates to ManpageViewer, fixed some bugs, implemented interface improvements, now it's easier to read the manpages, and the search system has also been improved. As you can see, I also adopted another name. I also expanded the scope, with the creation of "Custom Manpages," I can add the manpages of a specific software.

    man.nergahak.co.za/

    #man #manpages #FreeBSD #MINIX #NetBSD #OpenBSD #UNIX #pkgsrc #DataBase

  39. I wrote up a quick howto for getting bob up and running on OmniOS for someone, but figured it might be useful for others who want to play too.

    gist.github.com/jperkin/720751

    Quite a minimal, stripped-back config, so doesn't have dynamic jobs configured. Easy to add though if you want to push your system to the max.

    #pkgsrc #illumos #omnios

  40. I wrote up a quick howto for getting bob up and running on OmniOS for someone, but figured it might be useful for others who want to play too.

    gist.github.com/jperkin/720751

    Quite a minimal, stripped-back config, so doesn't have dynamic jobs configured. Easy to add though if you want to push your system to the max.

    #pkgsrc #illumos #omnios

  41. I wrote up a quick howto for getting bob up and running on OmniOS for someone, but figured it might be useful for others who want to play too.

    gist.github.com/jperkin/720751

    Quite a minimal, stripped-back config, so doesn't have dynamic jobs configured. Easy to add though if you want to push your system to the max.

    #pkgsrc #illumos #omnios

  42. I wrote up a quick howto for getting bob up and running on OmniOS for someone, but figured it might be useful for others who want to play too.

    gist.github.com/jperkin/720751

    Quite a minimal, stripped-back config, so doesn't have dynamic jobs configured. Easy to add though if you want to push your system to the max.

    #pkgsrc #illumos #omnios

  43. I wrote up a quick howto for getting bob up and running on OmniOS for someone, but figured it might be useful for others who want to play too.

    gist.github.com/jperkin/720751

    Quite a minimal, stripped-back config, so doesn't have dynamic jobs configured. Easy to add though if you want to push your system to the max.

    #pkgsrc #illumos #omnios