Date: Wed, 28 Mar 2007 16:03:46 -0500 From: "Corey Smith" <corsmith@gmail.com> To: "Gary Kline" <kline@tao.thought.org> Cc: Garrett Cooper <youshi10@u.washington.edu>, Pav Lucistnik <pav@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: A review of different port management tools : analysis for Google SoC project Message-ID: <8061fbee0703281403l4ffc9de8j30aef65ce77747ff@mail.gmail.com> In-Reply-To: <20070322174857.GA65365@thought.org> References: <4600AC05.4000004@u.washington.edu> <20070321050535.GB68447@thought.org> <1174518702.50979.2.camel@ikaros.oook.cz> <20070322174857.GA65365@thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ramblings of a long time FreeBSD user: * Use the pkg_* tools to manage the system binaries too: Imagine if installing the man pages would be as easy as: pkg_add -r freebsd-6.1-man or upgrading from 6.1-RELEASE to 6.2-RELEASE: portupgrade -o system/freebsd-6.1 freebsd-6.2 even better (use packages): portupgrade -PP -o system/freebsd-6.1 freebsd-6.2 See if anybody modified any system files: pkg_info -x ^freebsd6 -g * Make a cvs / portsnap tag that allows you to follow the tag of the last successful binary builds This way your ports collection and the binary packages available at $PACKAGEROOT are in sync. portupgrade -PP will have more success and it will make things like a gettext shlib bump easier to deal with. -Corey Smith
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8061fbee0703281403l4ffc9de8j30aef65ce77747ff>