Date: Thu, 9 Jun 2005 11:14:03 -0500 (CDT) From: Tony Shadwick <tshadwick@goinet.com> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade, automake14 -> automake19 Message-ID: <20050609111300.A71755@mail.goinet.com> In-Reply-To: <20050609161145.GA70744@orion.daedalusnetworks.priv> References: <20050609110039.N71755@mail.goinet.com> <20050609161145.GA70744@orion.daedalusnetworks.priv>
next in thread | previous in thread | raw e-mail | index | archive | help
No, I was referring to the fact that I ran portupgrade on automake14 and it complains and says that it is deprecated and strongly encourages using automake19 instead. I was curious if I just deleted the automake14 port and installed automake19 if I would be wreaking havoc on my dependencies in other ports. On Thu, 9 Jun 2005, Giorgos Keramidas wrote: > On 2005-06-09 11:01, Tony Shadwick <tshadwick@goinet.com> wrote: >> Could someone give me a quick hint on switching from automake14 to >> automake19 using the ports tree without wreaking total havock on >> dependencies? :) > > If you are asking what portupgrade will do with the installed ports, > then there's nothing to worry about. Just run portupgrade -a and it > will take care of building the necessary auto* ports too. > > If you are using automake14 in software you write or build yourself > outside of the Ports tree, don't. For an example of what may go wrong, > see the misc/81558 problem report: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=81558 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050609111300.A71755>