Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48847 - [elixir] Bad package dependencies

Attached to Project: Community Packages
Opened by Baryshnikov Alexander (ElSan) - Saturday, 09 April 2016, 17:42 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 14 April 2016, 16:07 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Problem is that 'elixir' package has 'erlang' in its dependencies (not 'erlang-nox'), and it installs some useless (on server) packages like gstreamer, wxgtk and e.t.c . Also 'erlang-nox' and 'erlang' packages are conflicted.

Possible solutions:
a) change 'erlang' to 'erlang-nox' in 'elixir' dependencies
b) make virtual package 'erlang-base' which will be provided by 'erlang' and/or 'erlang-nox' packages

Additional info:
* package version(s) elixir-1.2.4-1, erlang-nox-18.3-1, erlang-18.3-1


Steps to reproduce:

try to install 'elixir' without wxgtk
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 14 April 2016, 16:07 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Saturday, 09 April 2016, 17:48 GMT
Won't work. See  FS#47796 
Comment by Baryshnikov Alexander (ElSan) - Saturday, 09 April 2016, 18:26 GMT
I think, that observer GUI (bug in previous comment) is not a real requiremens. Yes, it's used very often in tutorials, articles and others manuals, but de jure it's not required for minimal elixir installation.
Comment by Candy Gumdrop (CandyGumdrop) - Thursday, 14 April 2016, 13:54 GMT
 FS#47796  is invalid and should be reverted.

The "observer" is a feature of Erlang and is nothing to do with Elixir, but people are assuming it's an Elixir feature even though they're just calling the Erlang observer from Elixir code. The observer feature is not at all essential, otherwise there would be no point of the erlang-nox package at all. It's no more useful for Elixir than it is for Erlang.

"elixir" should only depend on "erlang-nox" since "erlang-nox" can always be replaced with "erlang" if graphical / development features such as the observer are desired. Headless usage of Erlang / Elixir should not depend on the graphical observer + mesa-libl, gtk2, wayland etc.

Loading...