Date: Wed, 14 Mar 2001 10:26:09 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: obrien@FreeBSD.org Cc: Maxim Sobolev <sobomax@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/netinet ip_output.c Message-ID: <15023.43441.129662.580239@nomad.yogotech.com> In-Reply-To: <20010313165058.A86712@dragon.nuxi.com> References: <20010313162107.C86088@dragon.nuxi.com> <200103140036.f2E0a8v15357@vic.sabbo.net> <20010313165058.A86712@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 2. In the case when small FreeBSD-specific bug found and fixed you will > > not have to re-download the whole thing. > > I don't follow you. For the most part, the only thing a port gets from > FreeBSD is shared libs. If you fixed a bug in the port itself, then yes, > you need the distfile. > > > 3. It's usually a certain time lag between port update and package > > appearance at ftp*.freebsd.org. > > Valid point > > > 4. You can compile packages for the several different releases, say > > -current for your notebook, -stable for a production machine 3-stable > > for your grandma etc. > > This does not hold with your example. So don't bring up such cases. > > Nor are any of these cases ones Paul is mentioning.... Because he's running older software, using a pre-compiled version that is using 'newer' libraries, syscall mapping, etc.. is an issue. However, I don't know what the big deal is. I'm *still* running 2.2.8 on a box behind my firewall, and I still use the most recent ports tree. Sometimes I have to tweak with it a bit, but for the most part it 'just works'. (Again, this is FreeBSD 2.2, not 3.X, not even 4.X). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15023.43441.129662.580239>