Date: Thu, 29 Jun 2000 09:23:27 -0500 From: qa3507@email.mot.com (Takeshi Morishima) To: taoka@infonets.hiroshima-u.ac.jp, andrews@technologist.com Cc: qa3507@email.mot.com, ports@FreeBSD.org Subject: Re: net/xisp -> comms/xisp + new import of comms/yawmppp Message-ID: <200006291423.JAA01856@timbre.cig.mot.com> In-Reply-To: TAOKA Satoshi's message of "Thu, 29 Jun 2000 15:33:09 %2B0900" <20000629153309W.taoka@infonets.hiroshima-u.ac.jp> References: <20000628222044.B13914@argon.gryphonsoft.com> <200006290446.XAA24389@timbre.cig.mot.com> <20000629011914.F13914@argon.gryphonsoft.com> <20000629153309W.taoka@infonets.hiroshima-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
In message "Re: net/xisp -> comms/xisp + new import of comms/yawmppp"
on 00/06/29, TAOKA Satoshi writes:
> net/xisp/pkg/DESCR has the following sentence:
>
> The xisp package implements a user-friendly X interface to pppd/chat
> and provides maximum feedback from the dial-in and login phases on a
> browser screen, as well as a manual login terminal window.
>
> Note that it includes "pppd". And ports for ppp (e.g. ppxp, ppp-nt and
> so on) are in net category instead of comms.
>
> So I prefered net category rather than comms.
>
> Is that incorrect decision ? Do ports for ppp (e.g. ppxp, ppp-nt and
> so on) have to move into comms category, if so?
It wasn't an incorrect decision. Certainly net can be one of good
categories for xisp. The reason I think comms is more appropriate is
the fact that xisp does not do much about ppp protocol itself, but
implements an interactive login terminal emulator. I'd agree net is
the best place if it contains ppp driver. On the other hand, xisp is
not a "generic" comm program, it is specialised for pppd/chat. One can
argue that comms is not an appropriate place either. (In addition,
with xisp being in comms, it may be difficult for typical users to
find it through category.)
It's really how you think the category should be. Putting it in comms
seems appropriate from the development side point of view, and putting
it in net may be better from the user side point of view.
Regards,
Takeshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006291423.JAA01856>