From owner-freebsd-questions Tue Apr 25 15:36:27 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rdc1.sdca.home.com (ha1.rdc1.sdca.home.com [24.0.3.66]) by hub.freebsd.org (Postfix) with ESMTP id 6FF5937B6C6 for ; Tue, 25 Apr 2000 15:36:23 -0700 (PDT) (envelope-from jgowdy@home.com) Received: from cx443070a ([24.4.93.90]) by mail.rdc1.sdca.home.com (InterMail vM.4.01.02.00 201-229-116) with SMTP id <20000425223622.ZVIX9697.mail.rdc1.sdca.home.com@cx443070a>; Tue, 25 Apr 2000 15:36:22 -0700 Message-ID: <000701bfaf08$42d7c7a0$5a5d0418@vista1.sdca.home.com> From: "Jeremiah Gowdy" To: "Kristoph Yates" Cc: References: Subject: Re: Why does PORTS SUCK so BADLY!? Date: Tue, 25 Apr 2000 15:47:39 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4132.1800 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4132.1800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That is my question. It seems the idea behind ports is trapped in the > 70's. They hardly work and many times get errors about "file not > found" or something equally annoying.. so I have to go in and screw > with it "by hand" which is no problem for me.. but the newbies are > another story. Once I ran make lynx and it said I had to have X11 > installed. What a crock.. another fine example is openssl ... It > wants the useless RSAREF crap. What a crock! What does Satoshi Asami > have to say about the disorganization of the ports collection? When > will FreeBSD come up with something more reliable? Yes, I cvsup'd the > latest ports as of about a week ago. The only reason I would like to > see ports be more reliable is because I have lots-o-people that want > to run *nix.. so I recommend to them FreeBSD. If ports were more > reliable, I would spend less time on the phone/net helping people > install stuff on their FreeBSD boxes. So far, the easiest solution > is to tell them to try Linux. rpm --install blahblahblah seems to > work better for newbies than depending on the ports and these folks > are pretty brainless when it comes to installing things "by hand ", > the "old fashioned way". Any info would be appreciated. Please > respond via email as I am not subscribed to the list. thanks, > kyates@wspice.com > I must agree with the others on this. I've only had ONE time in which a port had some error. When I tried to install the latest Lynx, it said forbidden, because of bugs and backdoors. I simply changed the makefile to remove the forbidden, agreeing that I accepted the risks of running the port. Other than that, I've installed many many ports with absolute ease. I think ports are one of the greatest things about FreeBSD. If I want an SQL database server, I go to ports, make install mSQL or MySQL and bam, I'm in business. I want file sharing with Win9x clients ? I go to ports, samba, make install, and bam, I'm in business. With a fast perm internet connection, and a FreeBSD server I can grab hundreds of programs for almost every application with little or no trouble. In short, I think ports KFA. I think alot of people agree with me. If you don't like ports, you can feel free to download packages instead. No one is FORCING you to install the ports collection. I remember the question during the install, do you want the ports collection ? If you don't like it, don't install it and install all the shit by hand if it suits you. I don't know what all these weird problems you're coming up with are though. I have had almost none. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message