this post was submitted on 27 Apr 2024
39 points (85.5% liked)

Linux

47290 readers
1007 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 4 months ago (1 children)

For such a project, I think a different structure would make more sense. A structure where each supported package manager is a module on its own (like module/pacman.sh) and contains all the logic for this specific package manager. Those modules would only contain functions. And the main script with the main logic and loads in the module would not know or check what package manager it uses, but instead just runs the functions that are named the same in each module. But that would obviously require a major rewrite.

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago)

Makes sense and you're probably right, but I'll tell you why I didn't do it that way:

  1. I just did what came first to me
  2. I like the idea of the API defining the project structure
  3. When adding a new package manager, if that ever happens, I would like to see all other implementation of the same functionality on the same file, for help and inspiration