Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix messed client #135

Merged
merged 3 commits into from Nov 29, 2013
Merged

Fix messed client #135

merged 3 commits into from Nov 29, 2013

Conversation

jreidinger
Copy link
Member

No description provided.

Problem is that even if clients acts like script, it is evaluated in
global namespace and process is still alive, result is that it mess
global namespace. In this particular case it breaks installation because
it adds Yast::FileUtils to global namespace as ::FileUtils and when we
require original FileUtils from ruby, then it collide and raise
exception.
@@ -1,60 +1,63 @@
Yast.import "LanItems"
Yast.import "NetworkInterfaces"

include Yast
#enclose client into own namespace to prevent messign global namespace
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just a typo 'messing'

@lslezak
Copy link
Member

lslezak commented Nov 29, 2013

LGTM

jreidinger added a commit that referenced this pull request Nov 29, 2013
@jreidinger jreidinger merged commit 5b4ae3a into master Nov 29, 2013
@jreidinger jreidinger deleted the fix_messed_client branch November 29, 2013 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants