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

Incorrect package names for ruby-* gems #25

Open
jonhoo opened this issue May 8, 2015 · 2 comments · May be fixed by #26
Open

Incorrect package names for ruby-* gems #25

jonhoo opened this issue May 8, 2015 · 2 comments · May be fixed by #26

Comments

@jonhoo
Copy link

jonhoo commented May 8, 2015

pacgem ruby-progressbar installs a package named ruby-progressbar, and not ruby-ruby-progressbar as dictated by the Arch Gem package guidelines. This makes adding dependency on pacgem-installed packages harder, and leads to potential conflicts (i.e. there is both a progressbar and a ruby-progressbar gem, and pacgem would compile them to the same package name).

@jonhoo jonhoo linked a pull request May 8, 2015 that will close this issue
@minad
Copy link
Owner

minad commented May 20, 2015

I am not sure about this. Should we maybe remove the normalization alltogether?

"#{ruby_package}-#{gemname.downcase.sub(/^ruby-/, '').tr('_', '-')}"

Like downcase etc. Because this can in principle also lead to clashes.

@jonhoo
Copy link
Author

jonhoo commented May 20, 2015

I think at least the downcasing should be preserved. From the Arch packaging standards on package naming

Package names should consist of alphanumeric characters only; all letters should be lowercase.

Whether it makes sense to also convert underscores to dashes, I'm not sure. Judging from the Gem naming standard, _ and - have different semantic meanings, and so you could, in theory, have different packages differing only in their use of _ and -. Thus, it might be best if _'s aren't translated. I'm not sure if this breaks Arch dependencies though..

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 a pull request may close this issue.

2 participants