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

/etc/profile.d/bundler-exec.sh script breaks GNOME desktop on Arch Linux #30

Closed
ed-torvalds opened this issue Apr 15, 2016 · 7 comments
Closed

Comments

@ed-torvalds
Copy link

Your package bundler-exec (version latest-1) provides a fault script /etc/profile.d/bundler-exec.sh because of which I was not able to login to GNOME 3.20 on Arch Linux. More details: https://bbs.archlinux.org/viewtopic.php?id=211284
You must know that all the scripts in /etc/profile.d directory are run by sh at the time of login in GDM (usually because bash or zsh are default shell). sh shell does not allow - in the name of identifiers, so I get this error

Apr 13 14:36:59 ArchLinux /usr/lib/gdm/gdm-x-session[2719]: /etc/profile.d/bundler-exec.sh: line 12: `bundler-installed': not a valid identifier

you should please fix this problem asap :-) I have installed this package from https://aur.archlinux.org/packages/bundler-exec/
Fixing it requires to remove - from all identifiers

@gma
Copy link
Owner

gma commented Apr 15, 2016

Thanks for the report, but it's not intended to be dropped into a system wide folder (and I consider doing so – magically redefining a bunch of Ruby scripts for all users – a bad idea).

@gma gma closed this as completed Apr 15, 2016
@ed-torvalds
Copy link
Author

so what fix you are going to do in your package?

@gma
Copy link
Owner

gma commented Apr 15, 2016

What gave you the impression it's my package? I don't think this script is a good candidate for being packaged at all.

@gma
Copy link
Owner

gma commented Apr 15, 2016

Also, when you do identify the author of the package, I suggest trying not to sound so demanding (eg "fix it asap" and "so what are you going to do?"). Don't forget that people share this stuff for free, on their own time.

Have you considered fixing it yourself, then sharing the result?

1 similar comment
@gma
Copy link
Owner

gma commented Apr 15, 2016

Also, when you do identify the author of the package, I suggest trying not to sound so demanding (eg "fix it asap" and "so what are you going to do?"). Don't forget that people share this stuff for free, on their own time.

Have you considered fixing it yourself, then sharing the result?

@ed-torvalds
Copy link
Author

I wasn't being demanding did you notice the word please, and I used the word asap because this problem might affect many no. of people, so to stop them from being frustrated.

@gma
Copy link
Owner

gma commented Apr 15, 2016

Take it as feedback as to how you came across.

Sure, you said please. If that's why you said asap it was redundant – of course other people may be affected if it's in a distro. That's implicitly obvious.

Why you said it isn't really relevant. It's inappropriately pushy. I'm not having a go (or annoyed), I'm just aware that you could rub some people up the wrong way with that approach, and you might not realise it if nobody points it out.

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

No branches or pull requests

2 participants