4 ms·

As Graham Perrin pointed out in a reply, there are more such bugs in FreeBSD's pkgbase experiment. They were opened months ago, and they're still open. This i

by JdeBP 1y ago

As Graham Perrin pointed out in a reply, there are more such bugs in FreeBSD's pkgbase experiment. They were opened months ago, and they're still open. This is not a finished mechanism. Very clearly not. (-: * https://github.com/freebsd/pkg/issues/2414 https://github.com/freebsd/pkg/issues/2414

grahamjperrin 1y ago
> https://github.com/freebsd/pkg/issues/2414 https://github.com/freebsd/pkg/issues/2414 I wrote: "2414 intrigues me, however there's not enough for me to tell whether it's a pkg issue. "I do know that the big picture includes things being suitably prioritised; for this reason, and others, I have felt no need to bump 2414. "If additional info is required, they'll ask me in due course." – <https://www.reddit.com/r/freebsd/comments/1mct33f/comment/n641jnk/ https://www.reddit.com/r/freebsd/comments/1mct33f/comment/n6...>
grahamjperrin 1y ago
You may be unaware of the numerous freebsd-update bugs that will never be fixed. With regard to pkgbase, > … Graham Perrin … not a finished mechanism. Very clearly not. (-: My experience with pkgbase is clearly very different from your perspective. <https://lobste.rs/s/ikhfqq/pkgbase_removes_freebsd_base_system#c_vqcdnj https://lobste.rs/s/ikhfqq/pkgbase_removes_freebsd_base_syst...>: "… I should describe the pkgbase caboodle as ninety-eight percent production-ready. The official packages for FreeBSD-RELEASE have always been _one hundred percent_ production quality. Very few aspects of pkgbase are experimental."