Changing the name of a binary packaged application and its evoking command
Posted
by
jerkstore
on Super User
See other posts from Super User
or by jerkstore
Published on 2013-10-25T19:03:06Z
Indexed on
2013/10/25
21:59 UTC
Read the original article
Hit count: 152
I have taken the source code of a large project, App A, and made many modifications to it to produce my version, App B. Both App A and App B compile cleanly on Debian and Red Hat and now I would like to build binary packages for both platforms.
The last modification I need to make is ensuring App B can be installed alongside App A without any interference. I should be able to evoke both application-a
and application-b
in the terminal and have both be listed as separate software in whatever desktop environment is present.
The projects have a debian/
folder (containing rules
, control
, etc.) and an rpm/
folder containing a SPEC
file. Currently, building and installing the .rpm and .deb packages works except that App B is recognized as App A and therefore does not meet the aforementioned requirements. ldd
shows the programs have the same exact dependencies and I am not able to pursue static linking of libraries.
What modifications do I need to make to my project to achieve the desired outcome? Please be specific as I do not have much experience with the packaging process.
© Super User or respective owner