And of course I’m installing Linux on it. Install went well, even the fingerprint sensor built in to the laptop works.

Mostly this will be a school and DND machine but always nice to have a functional laptop for whatever else I may need it for.

  • T4V0@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 hours ago

    Everyone has their reasons for choosing the distro that they choose.

    That’s fine I suppose, though there are other distros more fitting if latest version isn’t of concern.

    And that isn’t a hassle. You sign up to it when you install Arch. If you aren’t willing to do that thing that takes a shorter time (loading up the Arch homepage) than actually issuing the upgrade command 😄, then yeah, Arch isn’t for you. Let’s concede that much, I suppose.

    I didn’t need to do that, I just used a RSS feed reader directly from the Arch news. Now, for an regular user, it would be a learning experience to actually be aware of possible manual interventions, especially since Arch makes upgrading a breeze, it’s not a thing in other distros.

    Right, again, that’s you creating maintenance for yourself. AUR is considered separate from the distro itself. I stand by my main point. 😁

    Actually, installing from the AUR is what helped me at the time, since the official software package was deprecated — removed from the main arch repository —, and I didn’t have time to repackage it myself. The deprecated package without a viable official replacement is what created a need to do system maintenance. And installing from the AUR was fine as long as you read the PKGBUILD, at least at the time. Regardless if either installing from the AUR, repackaging or downgrading the software were the solutions, it created friction with the end user. Which is fine for this particular distro, but for others in stable releases, it would be a major flaw.

    • Victor@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 hour ago

      I didn’t need to do that, I just used a RSS feed reader directly from the Arch news.

      Nice, that’s a great solution!

      Ah, I misunderstood what you were saying about installing that thing from the AUR then, in your example. I get it now.

      But to think that the deprecation was caused by… upgrading! 😆

      We’re very deep into this thread now and I’m sort of losing the plot, and it’s very late here. But these anecdotes I find are quite rare. Surely this would be happening in a non-rolling release as well. If Arch deprecated a package, and Debian were to do so for the same reason (seems likely, perhaps?), the only difference is the time frame in which you have to/choose to deal with it. If it disappeared from the Debian repo, you’d have to find some way of replacing it yourself, too.

      I might be misunderstanding you again, I feel. But I hope you see what I mean, in case I’m understanding the situation correctly.