You are not logged in.
Hi all! New user here.
I think I have found an inconsistency in maintaining the KISS principle for the gnuplot package, as it requires packages that are not essential. For example, if I were to only use gnuplot for CLI integration with pgfplots in LaTeX, I have installed at least 190 MB of dependencies more than the 3 MB the package itself consumes. Awkward examples of (meta-)dependencies for a plotting program include gstreamer, qt5-location, dconf and cdparanoia.
Neither the README or INSTALL files in the source tarball say anyhing about dependencies other than GNU readline, which is included in the core repo anyway.
My suggestion is that all of the currently listed dependencies be listed as optional. What can I do to help make it so?
From the Arch Linux wiki page:
Simplicity
Following The Arch Way philosophy, Arch Linux is lightweight, flexible, simple and aims to be very UNIX-like. A minimal environment (no GUI) compiled for i686/x86-64 architectures is provided upon installation: rather than tearing out unneeded and unwanted packages, the user is offered the ability to build up from a minimal foundation without any preemptively-chosen defaults. Arch's design philosophy and implementation make it easy to extend and mold into whatever kind of system is required, from a minimalist console machine to the most grandiose and feature-rich desktop environments available: it is the user who decides what his Arch system will be.
From The Arch Way wiki page:
Simplicity
Simplicity is the ultimate sophistication. — Leonardo da Vinci
Simplicity is absolutely the principal objective behind Arch development. Many GNU/Linux distributions define themselves as "simple." However, simplicity itself has many definitions.
Arch Linux defines simplicity as without unnecessary additions, modifications, or complications, and provides a lightweight UNIX-like base structure that allows an individual user to shape the system according to their own needs. In short: an elegant, minimalist approach.
A lightweight base structure built with high programming standards will tend to have lower system resource demands. The base system is devoid of all clutter that may obscure important parts of the system, or make access to them difficult or convoluted. It has a streamlined set of succinctly commented, clean configuration files that are arranged for quick access and editing, with no cumbersome graphical configuration tools to hide possibilities from the user. An Arch Linux system is therefore readily configurable to the very last detail.
Complexity without complication.
Arch Linux retains the inherent complexities of a GNU/Linux system, while keeping them well organized and transparent. Arch Linux developers and users believe that trying to hide the complexities of a system actually results in an even more complex system, and is therefore to be avoided.
Last edited by svenper (2015-05-02 15:28:33)
Offline
If gnuplot can indeed run without installing those packages, you can file a bug report. But it could very well be that this requires disabling features at compile time. That is something that might also be open to discussion (feature (removal) request), but the goal is not to have the smallest packages with minimal dependencies (there are other distros that focus on being small). Packages in the repos should satisfy most users and those who require exotic features or want to obsess over keeping everything minimal or consistent with their personal definition of KISS can rebuild packages to suit their needs.
I don't see those "awkward examples" in the dependency list; I assume they're further down in the dependency tree?
Offline
https://projects.archlinux.org/svntogit … 4bb08c80a3
Edit: Try https://aur.archlinux.org/packages/gnuplot-nox/ or https://aur.archlinux.org/packages/gnuplot-notk/
Last edited by karol (2015-05-01 18:26:25)
Offline
Wow. I sure feel stupid missing that. Thanks!
(What are they doing in the AUR?)
Edit 1: I was originally writing a long post about qt5 having unreasonable dependencies but I didn’t feel that was leading anywhere.
Edit 2: From the Wiki:
Simplicity
Following The Arch Way philosophy, Arch Linux is lightweight, flexible, simple and aims to be very UNIX-like. A minimal environment (no GUI) compiled for i686/x86-64 architectures is provided upon installation: rather than tearing out unneeded and unwanted packages, the user is offered the ability to build up from a minimal foundation without any preemptively-chosen defaults. Arch's design philosophy and implementation make it easy to extend and mold into whatever kind of system is required, from a minimalist console machine to the most grandiose and feature-rich desktop environments available: it is the user who decides what his Arch system will be.
So no, I don’t think this thread is me "obsess[ing] over keeping everything minimal or consistent with [my] personal definition of KISS".
Last edited by svenper (2015-05-02 15:21:36)
Offline
What are they doing in the AUR?
Usually we only have one version of a package in the repos, with AUR and ABS providing all the variants you want.
Offline
^
if you do not like how something is compiled there is abs.
Last edited by bleach (2015-05-02 02:51:39)
Offline