Bug 18454 - 'netcat' and 'nedit' ports conflict.
Summary: 'netcat' and 'nedit' ports conflict.
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-05-08 22:00 UTC by matt
Modified: 2000-05-29 04:59 UTC (History)
0 users

See Also:


Attachments
file.diff (696 bytes, patch)
2000-05-08 22:00 UTC, matt
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description matt 2000-05-08 22:00:00 UTC
The netcat port installs the binary to /usr/local/bin/nc. This location
conflicts with the nedit port which installs the server binary to the
location /usr/X11R6/bin/nc. Though these are different locations, they
cause problems relating to which gets called in the path. I find this 
far less than ideal.

Fix: I've decided to patch to change the netcat install to 'netcat', you may
prefere to change nedit's server binary instead. I'll leave that up to
you to decide what is best.
How-To-Repeat: 
Install both nedit and netcat and type "nc", depending on how your path
is laid out, you will either net netcat or the nedit server :)
Comment 1 Bill Fumerola 2000-05-08 22:01:45 UTC
On Mon, May 08, 2000 at 08:56:49PM -0000, matt@ARPA.MAIL.NET wrote:

> diff -ur netcat.orig/Makefile netcat/Makefile
> --- netcat.orig/Makefile        Thu Apr 20 16:19:33 2000
> +++ netcat/Makefile     Mon May  8 16:55:17 2000
> @@ -23,7 +23,7 @@
>  ALL_TARGET=    freebsd
>  
>  do-install:
> -       ${INSTALL_PROGRAM} ${WRKSRC}/nc ${PREFIX}/bin
> +       ${INSTALL_PROGRAM} ${WRKSRC}/nc ${PREFIX}/bin/netcat
>  .if !defined(NOPORTDOCS)
>         @${MKDIR} ${PREFIX}/share/doc/netcat \
>                 && ${CHMOD} a+rx ${PREFIX}/share/doc/netcat

No.

-- 
Bill Fumerola - Network Architect / Computer Horizons Corp - CVM
e-mail: billf@chc-chimes.com / billf@FreeBSD.org
Comment 2 matt 2000-05-08 22:05:36 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 8 May 2000, Bill Fumerola wrote:
[...]
: No.

Understood, it was just one idea to the problem (and the solution that I
took personally) I suppose I can understand why it would not be ideal. The
fact remains that having ports that conflict with eachother is not ideal,
so a solution is needed.

: -- 
: Bill Fumerola - Network Architect / Computer Horizons Corp - CVM
: e-mail: billf@chc-chimes.com / billf@FreeBSD.org

Regards,

Matt Heckaman
matt@arpa.mail.net
http://www.lucida.qc.ca

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (FreeBSD)
Comment: http://www.lucida.qc.ca/pgp

iD8DBQE5FywidMMtMcA1U5ARAtkUAKDGVJJGhP0jMIOhTTnybHbEcb6QAwCg1SVh
JTYMn3yfmv7BiWRTcM/uDvs=
=j+rv
-----END PGP SIGNATURE-----
Comment 3 Bill Fumerola 2000-05-08 22:28:09 UTC
On Mon, May 08, 2000 at 05:05:36PM -0400, Matt Heckaman wrote:

> : No.
> 
> Understood, it was just one idea to the problem (and the solution that I
> took personally) I suppose I can understand why it would not be ideal. The
> fact remains that having ports that conflict with eachother is not ideal,
> so a solution is needed.

I know. I shouldn't have been as blunt, but I think this issue has come up
before. Too many people are used to typing "nc".

-- 
Bill Fumerola - Network Architect / Computer Horizons Corp - CVM
e-mail: billf@chc-chimes.com / billf@FreeBSD.org
Comment 4 matt 2000-05-08 22:38:01 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 8 May 2000, Bill Fumerola wrote:
[...]
: I know. I shouldn't have been as blunt, but I think this issue has come up
: before. Too many people are used to typing "nc".

Ack. My bad. When I did the mailing list search it appears that I forgot
to check "ports" as well as questions/stable. Now that I read back on the
posts, I see that you are correct in that it was brought up before in Dec
1999. You're also right about too many people being used to typing "nc"

[from archives]
> Date:      Sun, 2 Jan 2000 17:16:43 -0800
> From:      "David O'Brien" <obrien@freebsd.org>
> To:        freebsd-ports@freebsd.org
> Subject:   Re: editors/nedit vs. net/netcat
> Message-ID:  <20000102171643.A57182@dragon.nuxi.com>
[...]
> Nope.  Netcat has been around alot longer than nedit, thus it is
> installed as ``nc'' on Suns, HP's, etc.. already.  `nc' is the name it
> is known as, plain and simple.  Plus netcat is often used in scripts,
> which would break with a name change.
>
> Why not ask the Nedit people to pick a new name for `nc'?  `nclient' or
> something would be just fine.  People demanding a shorter name can make
> an alias.
> 
> -- 
> -- David    (obrien@NUXI.com)

This makes alot of sense and is most likely a much better solution. Either
way it still needs to be implimented and most likely done on our side as I
do not know how much luck there would be in talking the nedit people into
changing it. Note: No offense intended in any way to anyone on the nedit
team, it's a great editor.

Matt Heckaman
matt@arpa.mail.net
http://www.lucida.qc.ca

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (FreeBSD)
Comment: http://www.lucida.qc.ca/pgp

iD8DBQE5FzO6dMMtMcA1U5ARAnG+AJ44FiWRR6BoatuVH2YAmeJYqYVT+QCgvzny
6HgkT/Pw3uy/zUusFQmUY0o=
=xwg6
-----END PGP SIGNATURE-----
Comment 5 Steve Price freebsd_committer freebsd_triage 2000-05-29 04:58:28 UTC
State Changed
From-To: open->closed

I've changed the nc to nclient in the nedit port.