pkg

> 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/n6...>

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

I found DPDK and FreeBSD's pkg package manager to be very clean and educational. Reference http://www.dpdk.org and https://github.com/freebsd/pkg

one more, FreeBSD's pkg uses picosat - https://github.com/freebsd/pkg/tree/master/external/picosat

I hope more command-line interfaces adopt a similar pattern. I pet peeve of mine is searching for a package (irrelevant of the package manager) and then installing it. In terms of interaction, it goes on something like this: $ ${tool} search ${pattern} res1 res2 res3 # I'm interested in the first and last package names. $ ${tool} install <grab mouse> <double-click res1> <shift-insert> <double-click res3> <shift-insert> # On a side-note, this can also be done with tmux copy-mode by appending the # results to a buffer, but I personally find that using the mouse is faster # in this case. Enumerating the results of the search and doing a '${tool} install %1 %3' would be a huge improvement. I once offered to add [1] such functionality to freebsd binary package manager, but nothing came out of it (perhaps for good re

Not to mention that you can use straight ports of Debian apt-get[1], FreeBSD pkg-ng[2], or even Arch pacman[3] on OS X if you so desire. 1: http://pdb.finkproject.org/pdb/package.php/apt 2: https://github.com/freebsd/pkg 3: https://github.com/kladd/pacman-osx

A lot of non-Free software also disallows redistribution, so it's not permissible to put it in the binary repository. It's possible that free but not Free (e.g., zero-cost binary-only software) software could be included in the repository. pkg metadata does include license information -- see https://github.com/freebsd/pkg/issues/20, but I am not sure of plans to provide user-facing control over acceptable licenses at the moment. It's a good idea though and I'll see if we can make it happen.

This change was written by Landon Fuller, one of the founders of MacPorts. There's an explanation for it in a comment on the pull request: https://github.com/freebsd/pkg/pull/1113#issuecomment-680639... This change doesn't mean very much in isolation, but will hopefully be the beginning of some interesting collaboration by packagers on both platforms.

Yes -- FreeBSD 10 has a new package manager which you can use to install pre-compiled binaries (a la `apt`). If you want to read more about it: https://wiki.freebsd.org/pkgng https://wiki.freebsd.org/PkgPrimer http://www.freebsd.org/doc/handbook/pkgng-intro.html https://github.com/freebsd/pkg