From owner-freebsd-questions@FreeBSD.ORG Mon Jul 19 14:14:06 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D86ED16A4CE for ; Mon, 19 Jul 2004 14:14:06 +0000 (GMT) Received: from outbox.allstream.net (outbox.allstream.net [207.245.244.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id A97ED43D2D for ; Mon, 19 Jul 2004 14:14:06 +0000 (GMT) (envelope-from epilogue@allstream.net) Received: from localhost (mon-pq58-164.dial.allstream.net [216.123.143.68]) by outbox.allstream.net (Allstream MTA) with SMTP id D8A83EB2CD; Mon, 19 Jul 2004 10:14:04 -0400 (EDT) Date: Mon, 19 Jul 2004 10:13:39 -0400 From: epilogue To: Travis Poppe Message-Id: <20040719101339.7d59f8e8@localhost> In-Reply-To: <20040719090626.Q97752@chylonia.3miasto.net> References: <20040719002221.21b6b9a3@maya.liquidx.org> <20040719090626.Q97752@chylonia.3miasto.net> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: Our package system: "Fundamentally Flawed" - A Linux User. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 14:14:07 -0000 On Mon, 19 Jul 2004 09:09:28 +0200 (CEST) Wojciech Puchar wrote: > > a different library name) like it should, pkg_add only gives a warning > > and an assumption that the install went well. > > > > Now, the user goes to run the package and gets a big fat error: > > libintl.so.X not found. > > package 0.13 should be compatible with 0.12 or should has name 1.* > > anyway - in 99.99% times > ln -s libintl.so.X libintl.so.Y where Y is required number > works :) another fix to this problem is to issue pkgdb -fu, then indicate for the program to depend on whatever collections you have installed. > > > > For a user like myself, this is no problem. I can recognize the error > > and figure out how to fix it manually. For a user considering switching > > to FreeBSD from Linux, this is considered a "fundamental flaw" in our > > package system and may lead to a very annoying flame war. Can this be > > fixed? Why hasn't it been fixed? i prefer this to consider this simply a different solution to a similar problem. when i bump into comments like this, i generally like to provide a link which (i think) very well outlines many of the important design differences between freebsd and linux. http://www.over-yonder.net/~fullermd/rants/bsd4linux/bsd4linux1.php it might seem a tad long, but it is a rewarding read. highly recommended. hope that this helps to dispel any misconceptions you may have. cheers, epi p.s. obviously any system (yes, even linux and bsd) can be improved. the question of _what_ to improve often boils down to 'how' (different solutions bring different trade-offs) and 'for what investment of time and energy' (not everything is equally urgent). > war requires 2 sides to fight. simplest way to avoid is ignore them. > > no one forces linux user to go to FreeBSD or otherBSD. > > > 2 years ago mostly because linux started "the only right" solution and to > be "better than windows" i switched to NetBSD. and found that this said > to be worse *BSD are actually better. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" >