Date: Mon, 13 Oct 2008 19:19:08 -0400 From: Sahil Tandon <sahil@tandon.net> To: freebsd-questions@freebsd.org Subject: Re: portupgrade failure Message-ID: <20081013231908.GB44050@shepherd> In-Reply-To: <fb6605670810131108h78caaf44nf12d1f711db93e39@mail.gmail.com> References: <20081003172624.GC6090@piglet.digitaltorque.ca> <20081004110255.4e05dbf1@baby-jane-lamaiziere-net.local> <fb6605670810131104h3f20797br52183de6f2a7d1f7@mail.gmail.com> <20081013180549.GA25442@icarus.home.lan> <fb6605670810131108h78caaf44nf12d1f711db93e39@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael P. Soulier <msoulier@digitaltorque.ca> wrote: > On Mon, Oct 13, 2008 at 2:05 PM, Jeremy Chadwick <koitsu@freebsd.org> wrote: > > So don't use it? :-) There are alternatives like portmaster. > > I suppose I prefer a single, reliable, supported tool for the system. > portupgrade seems to be pushed the most in all of the documentation > that I can find, so I went with it. Maybe I should dig into its guts > and find out how it works. Try portmanager; it has worked well for me. -- Sahil Tandon <sahil@tandon.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081013231908.GB44050>