Date: Mon, 07 Oct 2002 12:47:51 -0700 From: "Kevin Oberman" <oberman@es.net> To: John Kozubik <john@www.kozubik.com> Cc: Rus Foster <rghf@fsck.me.uk>, questions@FreeBSD.ORG Subject: Re: Proper way to upgrade packaes from ports Message-ID: <20021007194751.E077F5D04@ptavv.es.net> In-Reply-To: Your message of "Mon, 07 Oct 2002 12:21:53 PDT." <20021007122004.C22036-100000@www.kozubik.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Mon, 7 Oct 2002 12:21:53 -0700 (PDT) > From: John Kozubik <john@www.kozubik.com> > Sender: owner-freebsd-questions@FreeBSD.ORG > > > Rus, > > Please take a look at /usr/ports/sysutils/portupgrade, as it is the > appropriate tool for these sort of upgrades. > > Circumstantial evidence over the years has led me to believe that most > ports will actually successfully and without issue overwrite their > previous iterations that were also installed via the ports tree (lynx, > wget, things like that). This is often the case, but is demonstrably not true in many cases. Old header files and such can really break things in a manner that is very hard to track down. While portupgrade does not fully automate everything and does require some understanding of what is being done, especially in the databases, it's still a huge win. On the other hand, every time some thing is done to a port that portupgrade does not handle, usually whan a dependency is removed along with the dependent package, questions and stable are flooded with questions. But I would not like going back to pre-portupgrade days! R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021007194751.E077F5D04>