• thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    23
    arrow-down
    1
    ·
    3 months ago
    • On Linux systems, ensure the download process does not write outside the download directory

    What does that mean “On Linux systems”? Pacman is available for non Linux systems?

    • Thurstylark@lemm.ee
      link
      fedilink
      English
      arrow-up
      10
      ·
      3 months ago

      Pacman was birthed from the Arch ecosystem, but it’s built to be generalized so any project can use it if they choose.

      • tetris11@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        3 months ago
        arch = base.tarball[0] + pacman
         
        [0] 90% similar to all other linux tarballs
        
          • tetris11@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            3 months ago

            The base tarball that separates Arch from Debian or Gentoo differ in very minor structural ways, but the difference is the way they fetch, parse, and install packages is huge.

            Given this small difference in base tarballs, one can make the case the Arch codebase is the pacman codebase.

            • Thurstylark@lemm.ee
              link
              fedilink
              English
              arrow-up
              2
              arrow-down
              1
              ·
              3 months ago

              I mean… Yeah…? It’s not all that controversial to say that any distro is essentially just glue between several pieces of software…

              What’s your point?

              • tetris11@lemmy.ml
                link
                fedilink
                arrow-up
                1
                ·
                edit-2
                3 months ago

                (not quite sure where the hostility is coming from, but) if you agree that the base tarball of the distro is inconsequential, then one could argue that the package manager is the actual distro.

                That is, using pacman on Windows is akin to an Arch installation on windows.

                • Thurstylark@lemm.ee
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  3 months ago

                  Apologies, hostility wasn’t my intention, only seeking understanding.

                  Ya know, in the context of the software in a vacuum, sure. But I think I’ll ammend what I said earlier about what constitutes a distro:

                  IMO, It’s not just software that glues other existing software together into a contiguous OS, but also a staff, a community, a philosophy cast on that collection of software. A way of doing things and thinking about them. Decisions and the rationale for them, a history of iteration, user needs and how those needs are filled. Us soft squishy humans that make, maintain, modify, administer, use, and complain about the software.

                  Because I think that reducing a distro to only the software it produces or uses fails to paint the whole picture. The mechanisms used for managing the collection of software on any specific machine is only one part of a larger system.

                  Pacman isn’t the only part of Arch, and Arch isn’t just pacman. The same is true if you s/Arch/MSYS2/g on that statement.

                  • tetris11@lemmy.ml
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    3 months ago

                    I hear what you’re saying but I try my best to divorce a piece of art from its art fans and curators, because ultimately I don’t want to be sold into a doctrine on how I should see something, I just want to enjoy it.

                    I do agree that Arch is much bigger than its codebase (I just sometimes wish it wasn’t, with the sole exception of the Arch Wiki)