This is a discussion on Re: pkg_* tools - FreeBSD ; Kris Kennaway wrote: > On Mon, Aug 04, 2003 at 01:38:46PM -0700, David O'Brien wrote: > >>On Mon, Aug 04, 2003 at 01:19:57PM -0600, M. Warner Losh wrote: >> >>>Heck, we should just have sysinstall install portupgrade if that's the ...
Kris Kennaway wrote:
> On Mon, Aug 04, 2003 at 01:38:46PM -0700, David O'Brien wrote:
>>On Mon, Aug 04, 2003 at 01:19:57PM -0600, M. Warner Losh wrote:
>>>Heck, we should just have sysinstall install portupgrade if that's the
>>Considering how the Ports Collection has gotten to the point you can't do
>>anything post-initial-install w/o portupgrade; I totally agree.
> Please explain. I think this is FUD - nothing has come to depend on
> portupgrade, except that it provides useful features that the ports
> collection itself never has.
cc: trimmed and moved to chat@
The 'fontconfig' mess of recent XFree86 has made a royal mess of things,
and the common response I hear to that is, "the ports system is
fundamentally flawed and cannot be taught to deal with it, but
portupgrade can". However, the times that I've tried to install
portupgrade on a non-virgin system (i.e. a system that has been around
for a few months and has had many ports installed through the
traditional means), it winds up horribly screwing my installation and
leaving many things, most notably X, damaged and unusable. I've heard
the same horror stories from others around me.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "email@example.com"