[minicom-Bugs][314541] Naming conflict of runscript with OpenRC

[minicom-bugs at alioth.debian.org]

minicom-Bugs item #314541 was changed at 2013-12-12 19:45 by Adam Lackorzynski
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=100031&aid=314541&group_id=30018

Status: Open
Priority: 3
Submitted By: Benda Xu (heroxbd-guest)
Assigned to: Nobody (None)
Summary: Naming conflict of runscript with OpenRC 
Category: None
Group: None
Resolution: None


Initial Comment:
Dear developers,

I am a user of minicom for 7 years, thanks a lot for the nice tool.

Recently I am envolved in packaging of OpenRC[1], which has a binary /sbin/runscript serving as a shebang of all initscripts. The binary has the same name as /usr/bin/runscript shipped with minicom.

The upstream of OpenRC evaluated that thanks to the shebang nature, changing the location of or renaming /sbin/runscript would break all the existing initscripts of OpenRC, which is tedious to cope with.

We are interested in the opinion of minicom group on the possiblity of renaming /usr/bin/runscript to something else, or other solutions that may exist.

Cheers,
Benda

1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684396

----------------------------------------------------------------------

>Comment By: Adam Lackorzynski (al-guest)
Date: 2013-12-12 19:45

Message:
Hi,

I guess minicom uses it much longer :)

I do not mind renaming runscript to minicom-runscript, however, I'm not sure how much people depend on runscript being called runscript. My feeling would be that it would not be terribly many.  Debian packaging wise, we could start in sid and see what happens, and depending on the reaction(s) put this upstream or not.

Adam

----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=100031&aid=314541&group_id=30018