You are not logged in.
Pages: 1
How can something be both optional and a dependency? Shouldn't these optional dependencies be referred to plugins or something?
Offline
If you want extra functionality in app X, you may need a package Y that provides it through the API of app X. Plugin is IMO not structurally exactly the same: even if it enhances functionality of a core application, it is -- on the code level -- separated from it.
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
I think what bohoomil is trying to say is that the extra functionality for package X is dependent on the installation of package Y.
Offline
I think what bohoomil is trying to say is that the extra functionality for package X is dependent on the installation of package Y.
true but it's "extra" and not required. i always thought a dependency was something required or the program wouldn't run
Offline
WonderWoofy wrote:I think what bohoomil is trying to say is that the extra functionality for package X is dependent on the installation of package Y.
true but it's "extra" and not required. i always thought a dependency was something required or the program wouldn't run
In this case, certain functionality of the package will be unavailable if you do not install the optional dependency, so it is a dependency for that functionality.
Offline
I think what bohoomil is trying to say is that the extra functionality for package X is dependent on the installation of package Y.
Exactly.
@mamamia88 -- and you are right: unless you install a dependency, a certain part of an application's functionality is disabled (ergo: won't run).
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
Pages: 1