Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Using NetBSD’s pkgsrc everywhere I can

rubenerd.com

Post reply on HN
Print view View original

31–40 of 80 posts

Re: Using NetBSD’s pkgsrc everywhere I can

#31

Post by mulmen »

smoldesu wrote: post #27
mulmen wrote: post #21

Earlier quoted context omitted.

In addition to the valid criticisms in sibling comments: I don’t like that it changes the rules on file ownership in /opt and /usr/local. And it’s petty but I really don’t appreciate the beer brewing metaphor. It doesn’t fit and it feels forced. Giving the project a searchable name is fine but cutesy names are irritating when I have real work to do. Just name the tool and especially commands for what they do. I say t…

I also hate the brewing metaphors. I don't know why MacOS developers feel so compelled to abstract integral parts of your program away into unrecognizable metaphors. It's like asking for ketchup at the counter of a diner, and they insist that they only have "Heinz Tomato Sauce". Nobody in real life does this because nobody likes a smartass, so it completely escapes me why people think it's suddenly okay to do in soft…

It's more like using a plumber analogy to make sandwiches. I mean plumbers eat lunch right? So we can refer to condiments as grout and bread and meat as tiles and pipes are the sandwiches because plumbing.

Want a Reuben? That's:

  plumber tile rye beef-corned
  plumber grout saurkraut russian
Also since this is in the context of making a sandwich a bunch of options to 'plumber' mention things like toaster oven wattage and temperature.

  set PLUMBER_PREHEAT=350
  set PLUMBER_BACKEND=toaster
This is all kind of a pain. Let's use pipes. Except for some reason whoever defined this uses thousand island instead of russian dressing and expects the sandwich on a plate.

  plumber pipe reuben --russian --to-go

Re: Using NetBSD’s pkgsrc everywhere I can

#32

Post by smoldesu »

mulmen wrote: post #31
smoldesu wrote: post #27

Earlier quoted context omitted.

I also hate the brewing metaphors. I don't know why MacOS developers feel so compelled to abstract integral parts of your program away into unrecognizable metaphors. It's like asking for ketchup at the counter of a diner, and they insist that they only have "Heinz Tomato Sauce". Nobody in real life does this because nobody likes a smartass, so it completely escapes me why people think it's suddenly okay to do in soft…

It's more like using a plumber analogy to make sandwiches. I mean plumbers eat lunch right? So we can refer to condiments as grout and bread and meat as tiles and pipes are the sandwiches because plumbing. Want a Reuben? That's: plumber tile rye beef-corned plumber grout saurkraut russian Also since this is in the context of making a sandwich a bunch of options to 'plumber' mention things like toaster oven wattage an…

Thanks for clearing this up. I don't make sandwiches very often, but putting it in plumbing terms made it a lot easier to digest!

Re: Using NetBSD’s pkgsrc everywhere I can

#34

Post by jmclnx »

sally1620 wrote: post #20

I wonder if anyone is going to create a linux distribution with a base system baked in with pkgsrc managing the applications. It would be very useful for containers and WSL.

I always liked its concept and I am surprised very few projects are using it. On NetBSD it works well, I guess NIH (https://en.wikipedia.org/wiki/Not_invented_here) syndrome :(

Re: Using NetBSD’s pkgsrc everywhere I can

#35

Post by hedora »

mulmen wrote: post #21
nerdponx wrote: post #14

Earlier quoted context omitted.

I'm always interested to try different things, but I don't understand why people seem to dislike Homebrew so much. I've been a mostly-happy user on both Mac and Linux for years.

In addition to the valid criticisms in sibling comments: I don’t like that it changes the rules on file ownership in /opt and /usr/local. And it’s petty but I really don’t appreciate the beer brewing metaphor. It doesn’t fit and it feels forced. Giving the project a searchable name is fine but cutesy names are irritating when I have real work to do. Just name the tool and especially commands for what they do. I say t…

I still don’t understand why sometimes I must type “cask” and sometimes I must not type “cask”.

No, I didn’t RTFM; I’m sure that would help, but I mostly just avoid homebrew when I can, and that’s worked out OK.

Re: Using NetBSD’s pkgsrc everywhere I can

#36

Post by weitzj »

I used it with Netbsd 1 and it was the first thing to install in Solaris.

Other question: how does one handle detection whether upgrades exist? Something like renovatebot but using pkgsrc. Or what is the best way in 2021 to trigger fresh builds against the latest packages?

Re: Using NetBSD’s pkgsrc everywhere I can

#37

Post by mulmen »

smoldesu wrote: post #32
mulmen wrote: post #31

Earlier quoted context omitted.

It's more like using a plumber analogy to make sandwiches. I mean plumbers eat lunch right? So we can refer to condiments as grout and bread and meat as tiles and pipes are the sandwiches because plumbing. Want a Reuben? That's: plumber tile rye beef-corned plumber grout saurkraut russian Also since this is in the context of making a sandwich a bunch of options to 'plumber' mention things like toaster oven wattage an…

Thanks for clearing this up. I don't make sandwiches very often, but putting it in plumbing terms made it a lot easier to digest!

I do like the idea of a tool named plumber with leaky abstractions.

Re: Using NetBSD’s pkgsrc everywhere I can

#38

Post by kelp »

znpy wrote: post #24
kelp wrote: post #15

Earlier quoted context omitted.

I dislike it because it’s really slow to do everything. Even printing help text is slow. Contrast with pacman on Arch, which is incredibly fast at nearly every operation. Unfortunately I’ve found all the package managers for macOS to be lacking. brew is slow, but has packages for most things and generally up to date. fink packages seem a bit out dated last I checked. At least the ones I cared about. MacPorts is also…

> pkgsrc doesn’t have Apple M1 binary packages available yet. basing this reply on my past experience with pkgsrc (in a netbsd or linux environments though) as long as you can point pkgsrc to a decent compiler and it can complete its bootstrap phase, it'll likely work.

That sounds right. But then I'm having to compile all the packages I need, which makes it even much much slower than brew when binaries are available.

Re: Using NetBSD’s pkgsrc everywhere I can

#39

Post by jayp1418 »

pxc wrote: post #5

I'd been wondering how good pgksrc is on macOS for a little while, previously having used Homebrew wherever Nixpkgs was inconvenient or incomplete. Could pkgsrc could be a better choice? pkgsrc is relatively nice for a cross-platform, source-based package manager in the old style, in that it provides convenient binary caches for most use cases. I wonder: Has the writer of the post in the OP tried any next-gen source-…

Check this : https://pkgsrc.joyent.com/install-on-osx/

Re: Using NetBSD’s pkgsrc everywhere I can

#40

Post by zephyr9 »

protomyth wrote: post #30

Does pkgsrc have "port variants" like macports?

Not for prebuilt binaries (variants are just separate packages) but because the pkgsrc repo is just a collection of Makefiles, you can cd into the directory and run

    bmake show-options
Then set PKG_OPTIONS.somepkg and

    bmake install
Or even just edit the Makefile.
Post reply on HN