On Tue, Jul 7, 2009 at 9:31 AM, Thorsten Toepper<atsutane@freethoughts.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
jezra wrote:
There is indeed a conflict of /usr/bin/sap. What is the best way to proceed in a situation such as this? Should I rename my binary or should I just put the name of the conflicting binary into "conflicts"?
You should also rename your package, the current PKGBUILD conflicts itself.
- -- Jabber: atsutane@freethoughts.de Blog: http://atsutane.freethoughts.de/ Key: 295AFBF4 FP: 39F8 80E5 0E49 A4D1 1341 E8F9 39E4 F17F 295A FBF4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iFYEARELAAYFAkpTeFcACgkQOeTxfyla+/TtKgDfVClv3hniaQw7HEeh2Fbu7TV8 TJXrN43Qi/l6rADfXCaBjSIhUOC6Xs48sos5BdN1DUp38+4pLIoBXQ== =INkt -----END PGP SIGNATURE-----
Unfortunately, after renaming the package and the compiled binary, I needed to edit and rename the man page and the associated help directives in the source code to reflect the changes to the package and binary name. Since I don't wish to step on anyone toes regarding application name collision, I'll hold off on submitting the PKGBUILD.