From: Bob Phan <bob@endlessrecursion.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] conflicting executable names
Date: Wed, 13 Mar 2002 12:18:22 +0000 (/etc/localtime) [thread overview]
Message-ID: <Pine.LNX.4.21.0203131202260.15682-100000@lucifer.evil-core.com> (raw)
What would the gentoo policy be to handle applications that want to use
the same executable name, but do not perform the same function and are
not interchangable.
For example, I wanted to quickly package up rename
(http://www.ibiblio.org/pub/Linux/utils/file/rename-1.1.tar.gz)
It is a slick little utility that allows you to rename a bunch of
files based on extended regexs (there's a review on www.unixreview.com).
Anyway, the executable it creates is named 'rename' which conflicts with
rename from sys-apps/util-linux. How should this be treated? For the
moment, I'm just calling it Rename.
--
/*
* Bob Phan <bob@endlessrecursion.net,rphan@nrgn.com>
* Computational Chemistry Informatics
* Neurogen Corporation
* (203)488-8201 x4645
*
* To understand recursion, you must first understand recursion.
*/
next reply other threads:[~2002-03-13 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 12:18 Bob Phan [this message]
2002-03-13 23:33 ` [gentoo-dev] Keychain wonderings Brent Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0203131202260.15682-100000@lucifer.evil-core.com \
--to=bob@endlessrecursion.net \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox