Date: Wed, 6 Feb 2008 18:08:31 -0600 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: navneet Upadhyay <navneet.upadhyay@gmail.com>, freebsd-ports@freebsd.org, freebsd-questions@freebsd.org, freebsd-binup@freebsd.org Subject: Re: Upgrading the Installed package Message-ID: <20080207000831.GO62553@over-yonder.net> In-Reply-To: <20080206095133.GA94134@eos.sc1.parodius.com> References: <1563a4fd0802052211h623de132q68a1ad0c8a9b930c@mail.gmail.com> <230174700802060040x4f2a0815r1a4bdc7fccf62b5d@mail.gmail.com> <20080206095133.GA94134@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 06, 2008 at 01:51:33AM -0800 I heard the voice of Jeremy Chadwick, and lo! it spake thus: > > So let's tell Navneet exactly what he's getting into, shall we? OK, but let's do that by telling him what he's getting into, not vague gestures at overblown half-truths. > - Ruby is not included in the base system; you have to install it > from ports (read: just another thing to have to maintain...) My workstation has about 800 ports installed. A relatively lean server has 300. 1 more is so deep in the noise, you can't hardly measure it, much less see it. > ports base system: > - C-based, and includes all of the pkg_* utilities. Nearly every > FreeBSD user/administrator is familiar with these tools. Can't upgrade things. Show me how I use pkg_* to upgrade a package (let's say, gtk), and have all the metadata set right afterward. Requires either stupid amounts of manual work, or a lot of scripting (I upgrade perl. How do I rebuild p5-*?). > portupgrade: > - Maintains its own database of ports installed, dependencies, and > so on -- COMPLETELY separate from that of the ports base system. Which is just a cache of the existing files, and can be blown away at any time with no consequences other than a minute or two remaking them. > - Said database must be kept in sync with ports base system > dependencies and other whatnots; and if they go out of sync Which it rebuilds when it notices is out of date. The only time I've had problems out of it in years of using portupgrade is when I do something like update BDB (or less often, portupgrade or ruby-bdb). Whoopie. Consider the recent case involving sudo and portmaster; when you use a tool to update a low-level piece of itself, you have to take some care how you go about it. > - Said database is Berkeley DB-based, which means you have to install > Oracle/Sleepycat BDB from ports. (I believe you can pick DB1.x > which comes with libc, but it's not recommended due to bugs). So now we're up to 4 ports to install? If you can make that my biggest worry, I'll sent you a ginormous certified check first thing in the morning. There are a lot of things to hate in portupgrade, but let's don't pile handwaving anthills into mountains on top of that. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080207000831.GO62553>