6 ms·

While this is certainly true, have you used pkg in the last year or so? It's come on leaps and bounds. The solver is now on a par with apt's SAT-solver, and o

by rleigh 8y ago

While this is certainly true, have you used pkg in the last year or so? It's come on leaps and bounds. The solver is now on a par with apt's SAT-solver, and overall it's (IMO) almost as good as apt at this point.

bayindirh 8y ago
No, honestly I didn't. I've installed OpenBSD to a VM in the beginning of the year to learn it, but I had no time to either play or learn using it. Looks like I need to resume learning it. Thanks.
- ComputerGuru 8y ago
  OpenBSD isn’t using the pkg we are talking about, fwiw. You’ll need to install FreeBSD for that.
  - bayindirh 8y ago
    Thanks, will try FreeBSD first, then.
    - sverige 8y ago
      OpenBSD's package manager is actually really easy to learn and use. Even I can do it.
      - bayindirh 8y ago
        I will try both, promise. :) I also find OpenBSD's ideology more resonating to me.
      - ComputerGuru 8y ago
        OpenBSD's package manager comes unconfigured out of the box, though :(
        adamrt 8y ago
        Can you elaborate on this? I'm not sure which version added it but /etc/installurl is configured to use cdn.openbsd.org during install. Prior to this, I believe /etc/installurl was populated with the mirror you chose during install. That had been around for at least a couple/few versions, IIRC. Is there something else you are referring to? https://man.openbsd.org/installurl https://man.openbsd.org/installurl
- rleigh 8y ago
  I'd certainly not discourage having a play around with it! I started trying it out with FreeBSD 10.0 a few years back. pkg was rough around the edges back then. If you had a lot of packages installed, like lots of development tools and desktop environments, it wasn't hard to get it into a situation where it would segfault or run into dependency problems during an upgrade. Right now, with 11.2, I've not run into any crashes for a good 2-3 years or any intractable dependency problems in a good 2 years or more. It's probably not perfect, these are very complex tools which are hard to verify, but it's certainly eminently usable from the point of view of an admin/end user/casual ports contributor like myself. In fact, when upgrading from Ubuntu 18.04 to 18.10 a few weeks back, I did actually run into a problem with apt refusing to upgrade because it couldn't work out the upgrade path. I had to remove a few packages which were causing problems, then re-install them after the upgrade. Whether that was apt or the packages having genuinely broken dependencies I'm not sure since I didn't investigate in detail.

by rleigh 8y ago

bayindirh 8y ago

No, honestly I didn't. I've installed OpenBSD to a VM in the beginning of the year to learn it, but I had no time to either play or learn using it. Looks like I need to resume learning it. Thanks.

ComputerGuru 8y ago
OpenBSD isn’t using the pkg we are talking about, fwiw. You’ll need to install FreeBSD for that.
- bayindirh 8y ago
  Thanks, will try FreeBSD first, then.
  - sverige 8y ago
    OpenBSD's package manager is actually really easy to learn and use. Even I can do it.
    - bayindirh 8y ago
      I will try both, promise. :) I also find OpenBSD's ideology more resonating to me.
    - ComputerGuru 8y ago
      OpenBSD's package manager comes unconfigured out of the box, though :(
      - adamrt 8y ago
        Can you elaborate on this? I'm not sure which version added it but /etc/installurl is configured to use cdn.openbsd.org during install. Prior to this, I believe /etc/installurl was populated with the mirror you chose during install. That had been around for at least a couple/few versions, IIRC. Is there something else you are referring to? https://man.openbsd.org/installurl https://man.openbsd.org/installurl
rleigh 8y ago
I'd certainly not discourage having a play around with it! I started trying it out with FreeBSD 10.0 a few years back. pkg was rough around the edges back then. If you had a lot of packages installed, like lots of development tools and desktop environments, it wasn't hard to get it into a situation where it would segfault or run into dependency problems during an upgrade. Right now, with 11.2, I've not run into any crashes for a good 2-3 years or any intractable dependency problems in a good 2 years or more. It's probably not perfect, these are very complex tools which are hard to verify, but it's certainly eminently usable from the point of view of an admin/end user/casual ports contributor like myself. In fact, when upgrading from Ubuntu 18.04 to 18.10 a few weeks back, I did actually run into a problem with apt refusing to upgrade because it couldn't work out the upgrade path. I had to remove a few packages which were causing problems, then re-install them after the upgrade. Whether that was apt or the packages having genuinely broken dependencies I'm not sure since I didn't investigate in detail.