Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Dec 2007 10:42:43 -0500
From:      Steven Kreuzer <stevenkreuzer@yahoo.com>
To:        Ade Lovett <ade@FreeBSD.org>
Cc:        freebsd-ports@freebsd.org
Subject:   Limitations of Ports System
Message-ID:  <0F330142-A3CA-4E6E-84BD-FDE55A8E3AEE@yahoo.com>
In-Reply-To: <19341C6C-BF3A-4DFD-B8DF-87F4E92B0335@FreeBSD.org>
References:  <475F7390.9090509@gmail.com> <1022BEDA-8641-4686-AB1A-3FE2D688F47F@FreeBSD.org> <475FAC1F.1010401@gmail.com> <19341C6C-BF3A-4DFD-B8DF-87F4E92B0335@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This thread was called "results of ports re-engineering survey" but I  
figured I would start a new thread.

On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote:
>
>
> We *know* it can be done better.  We *know* the scaling limits of  
> the current system, and most of us are completely amazed it even  
> still works.
>
> If y'all want to make a difference, concepts and ideas we have  
> plenty of.  Code talks.

Out of curiosity, are any of these shortcomings documented anywhere? I  
have been using ports on my home machine for a long time and I've never
had any problems with it. I assume the issues come into play when you  
work with multiple systems you are trying to keep in sync, etc.

I would be interested in reading about some of the limitations people  
have run into when using ports.

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0F330142-A3CA-4E6E-84BD-FDE55A8E3AEE>