Description of problem:
wings ships a user_default module in
This module is loaded by the erl shell on every startup
and its commands made directly available from the erl shell.
However, user_default is probably more meant to be something
for a user to change, not for a software package to install
for all users.
And what will happen when the next piece of erlang software
decides to ship its own user_default.beam file? The load order
will decide which module will be activated, right?
I quite like the lm() command from wings' user_default module,
but shipping this file by default probably is not all that
great an idea.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. $ erl
2. 1> lm().
** exception error: undefined shell command lm/0
We probably should think up a useful packaging policy for
wings-1.4.1-5.git9a2473e.fc17 has been submitted as an update for Fedora 17.
wings-1.4.1-5.git9a2473e.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing wings-1.4.1-6.git9a2473e.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
wings-1.4.1-6.git9a2473e.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
wings-1.4.1-6.git9a2473e.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.