Use a different executable name #69

Closed
gioele opened this Issue Oct 6, 2013 · 4 comments

Comments

Projects
None yet
2 participants
@gioele
Contributor

gioele commented Oct 6, 2013

The current executable installed by launchy is, fair enough, launchy. This name clashes with the executable installed by the Launchy application [1], installed by various Linux distributions as /usr/bin/launchy (see [2], [3], [4]).

Could the executable in the gem be renamed to a different name to avoid this clash?

[1] http://www.launchy.net/
[2] http://packages.debian.org/wheezy/amd64/launchy/filelist
[3] http://packages.ubuntu.com/raring/amd64/launchy/filelist
[4] http://koji.fedoraproject.org/koji/rpminfo?rpmID=4227579

@copiousfreetime

This comment has been minimized.

Show comment Hide comment
@copiousfreetime

copiousfreetime Oct 30, 2013

Owner

I'm fine if distributions need to change the executable name. I'll ponder a name change. If I do change the name I'll need to do a major version bump.

Owner

copiousfreetime commented Oct 30, 2013

I'm fine if distributions need to change the executable name. I'll ponder a name change. If I do change the name I'll need to do a major version bump.

@gioele

This comment has been minimized.

Show comment Hide comment
@gioele

gioele Oct 31, 2013

Contributor

Do you mean a project name change or executable name change?

I cannot push the debian package for the launchy gem (and all the packages that depend on it) because of this name clash. The consensus on the devel ML is that we should just rename the executable and publish the package. Before doing that I would like to ask you if any of these executable name sound acceptable to you:

  1. ruby-launchy (my personal favourite)
  2. launchy-rb
  3. launchy.rb
  4. launchy-ruby (I would reserve this for some Ruby extension to the launchy docker application)

Or maybe you would like to have a completely different executable name?

Contributor

gioele commented Oct 31, 2013

Do you mean a project name change or executable name change?

I cannot push the debian package for the launchy gem (and all the packages that depend on it) because of this name clash. The consensus on the devel ML is that we should just rename the executable and publish the package. Before doing that I would like to ask you if any of these executable name sound acceptable to you:

  1. ruby-launchy (my personal favourite)
  2. launchy-rb
  3. launchy.rb
  4. launchy-ruby (I would reserve this for some Ruby extension to the launchy docker application)

Or maybe you would like to have a completely different executable name?

@copiousfreetime

This comment has been minimized.

Show comment Hide comment
@copiousfreetime

copiousfreetime Oct 31, 2013

Owner

I was only considering an executable name change. The project name is going to stay as it is.

My first thought was to change the bin file to launchy.rb or launchy-cli. I think I'll do a trawl through the existing rubygem archive and see if there is an un-documented convention and use that approach. Give me a few days. 😄

Owner

copiousfreetime commented Oct 31, 2013

I was only considering an executable name change. The project name is going to stay as it is.

My first thought was to change the bin file to launchy.rb or launchy-cli. I think I'll do a trawl through the existing rubygem archive and see if there is an un-documented convention and use that approach. Give me a few days. 😄

@copiousfreetime

This comment has been minimized.

Show comment Hide comment
@copiousfreetime

copiousfreetime Oct 2, 2015

Owner

Closing, I haven't heard anything packaging issues in a while. Feel free to reopen.

Owner

copiousfreetime commented Oct 2, 2015

Closing, I haven't heard anything packaging issues in a while. Feel free to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment