Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Mar 2003 15:33:49 -0500
From:      taxman <taxman@acd.net>
To:        Cliff Sarginson <cls@willow.raggedclown.intra>, FreeBSD Questions <FreeBSD-questions@FreeBSD.org>
Subject:   Re: Portupgrade -- revisited
Message-ID:  <200303021533.49566.taxman@acd.net>
In-Reply-To: <20030302192233.GA326@willow.raggedclown.intra>
References:  <20030302192233.GA326@willow.raggedclown.intra>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 02 March 2003 02:22 pm, Cliff Sarginson wrote:
> At the risk of being accused of a complainer.
> I will state here that my experiments in the use of portupgrade, have
> left me without a useable X system.
> Guess it is back to the CD's.
> Will the ports maintainers *please* make sure they release compilable
> ports..especially for the big mothers like X/KDE.

Cliff, it's worked fine for me.  I installed all of KDE3 from ports.  Got 
virtually no errors, but I did do it by uninstalling almost all of my 
installed ports.  So yes portupgrade for something that large did not work.
	 Try making packages out of what ports you have installed.  Then uninstalling 
and reinstalling them shouldn't be too bad.
	And you've got to understand the complexity problems involved here.  There 
are 8200 or so ports right now.  Each has as many as 60 dependencies (like 
kde).  This creates an incredible web that is very difficult to keep working.  
The ports maintainers do a great job of this in fact.
	What is nearly impossible is to have it work perfectly for every given 
individual installation that may have many thousands of individual 
configuration changes, versions, old binary, source cruft lying around.
	So as mentioned before, problems could easily be due to stuff only you have 
on your system.  Try building in a clean environment.  If you get the same 
error in a clean environment then a clear message to the port maintainer with 
how to repeat the problem is the only way for them to get it working.  It 
doesn't involve knowing how to code in the given language, just useful error 
messages.
	An "it doesn't work" is useless and does fall into the complainer side, even 
if you're not trying to.

Try that and then ask questions if you can't get something working.

Tim

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?200303021533.49566.taxman>