Community Packages

Please read this before reporting a bug:

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!

FS#57015 - [unicorn] Rename ruby-unicorn to ruby-unicorn-engine

Attached to Project: Community Packages
Opened by Anatol Pomozov (anatolik) - Monday, 08 January 2018, 18:41 GMT
Last edited by Levente Polyak (anthraxx) - Wednesday, 28 February 2018, 19:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Anatol Pomozov (anatolik)
Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


There is a standard practice to call ruby gem packages based on its upstream gem name.

ruby-unicorn that is currently in [community] corresponds to `unicorn-engine` gem thus the package should be called `ruby-unicorn-engine`.

Current name `ruby-unicorn` creates confusion with well known Ruby server called `unicorn`
This task depends upon

Closed by  Levente Polyak (anthraxx)
Wednesday, 28 February 2018, 19:50 GMT
Reason for closing:  Implemented
Additional comments about closing:  1.0.1-4
Comment by Anatol Pomozov (anatolik) - Tuesday, 27 February 2018, 15:24 GMT
I am going to drop `ruby-unicorn` package to avoid conflicts with `unicorn` gem package. Levente, feel free to re-add it with correct name.
Comment by Levente Polyak (anthraxx) - Tuesday, 27 February 2018, 15:37 GMT
Don't, unicorn isn't even in the official repos threfor not supported. Will take a look if backporting the upstream pack works out.
Comment by Anatol Pomozov (anatolik) - Tuesday, 27 February 2018, 17:58 GMT
I have plans to add `unicorn` gem to the official repos.

But even without it one should follow upstream naming. The gem name for this project is `unicorn-engine`.
Comment by Levente Polyak (anthraxx) - Tuesday, 27 February 2018, 18:15 GMT
I get it its not like i have amnesia, please don't bullshit with follow upstream naming:
You exactly know how the situation turned up and there was no such gem published, neither unicorn webserver anywhere AUR (so why even add it out of nowhere just because?) or repo. A project that did not publish its gem just used this name so it got packaged... and we landed where we are. Unlicky situation but please don't pretend you don't know how this happened. It was only renamed lately and its a in-dev situation no release that easily take it that way.
Instead of just bitching, you could actually try helping instead of threatening to remove it.