• 1 Post
  • 29 Comments
Joined 1 year ago
cake
Cake day: March 22nd, 2024

help-circle






  • cqst [she/her]@lemmy.blahaj.zonetolinuxmemes@lemmy.worldmacro
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    edit-2
    1 month ago

    systemd is an init system and just has not played the same role in the development of GNU/Linux distributions like GNU has. before systemd there was sysvinit, and there are number of alternate init systems. It’s not about system functionality that we name operating systems.












  • I’m and end user

    Yeah, we all are. What’s your point?

    End users are also developers. All computer users are developers. You are developing.

    user working for end users

    By making a script that lets me get backdoors and shitty packages with ease? The linux package distribution system is a nightmare, Debian is the least bad approach. There is basically always a better option to using a .deb file. If you come across something that isn’t packaged, I recommend Flatpak, building from source (and installing unprivileged), or using the developers vendored tarball (installing unprivileged).

    https://wiki.debian.org/SecureApt

    By using local .debs you lose the benefit of:

    Reproducible builds

    GPG checksums

    Stable release model

    debian security team




  • If you are getting your code straight from the author,

    Which is not what you are doing at all with a .deb file. A .deb file is a binary with a bunch of scripts to “properly” install your package. Building from source is what you SHOULD be doing. Debian has an entire policy handbook on how packages are supposed to be packaged. Progrmatically you can review the quality of a package with ‘lintian’. .debs made by developers following a wiki tutorial can’t even come close. remember, apt installs happen as root and can execute arbitrary code.

    Also, debian packagers can be project maintainers, so they can be “the author.”