Re: before new version
Date: Sat, 3 Nov 2012 17:20:26 -0500 From: ajtiM lum...@gmail.com To: Polytropon free...@edvax.de Cc: freebsd-questions@freebsd.org Subject: Re: before new version Message-ID: 201211031720.27182.lum...@gmail.com Content-Type: Text/Plain; charset=iso-8859-1 On Saturday 03 November 2012 14:11:22 you wrote: BTW: packages are almost all the time outdated. The packages in the RELEASE directory and on the installation media meet the frozen ports tree (frozen _prior_ to the release date), so yes, they are a bit outdated, but they are considered mostly stable and usable when in use with what is distributed. On the server, both _those_ packages _and_ those in Latest/ (which are periodically built from the advancing ports tree after the release date) are often considered not _that_ current as if you would use CVS or SVN to obtain the bleeding edge latest ports tree and build from source. I didn't complain about bleeding edge sofware which we anywhere don't have (Gimp, Xorg, LibreOffice and all dependencies for those applications and more and more which I don't use and I don't need) but I complain about freezing ports too early before new release came out and after that rebuilt 5000 ports for example just because png new version is coming out. Or am I wrong? So yes, you could say what you said. :-) Mitja http://www.redbubble.com/people/lumiwa Your complaint seems to be unfair to me as this is the first time -- as far as I remember -- that the ports freeze was implemented only for RC2 but not already for RC1. So, the tree is certainly not frozen too early. C-S ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: before new version
On Sat, 3 Nov 2012 11:23:12 -0500, ajtiM wrote: Hi! Could someone explain, please why ports should be frozen before a new version of FreeBSD came out? The idea is to make sure that RELEASE can be shipped with installation media (CD, DVD) for offline use which requires ports mostly to be tested and working in some specific state, and then the packages (those you can access on the installation media) are generated from them. It's handy for systems that do not have Internet access to install software off-line. It happened all the time and after update (if you update or not) there are so many ports for updating. In case for very long waiting for version 9.1 will be thousands of them. That could probably be. Most users who have Internet access and run servers (and also home systems) will tend to update the OS beyond RELEASE and also do so with the ports collection, or alternatively also use pkg_add -r from the Latest/ directory instead of RELEASE (which _always_ contains the ports generated from the frozen ports tree). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: before new version
On Saturday 03 November 2012 12:18:35 Polytropon wrote: On Sat, 3 Nov 2012 11:23:12 -0500, ajtiM wrote: Hi! Could someone explain, please why ports should be frozen before a new version of FreeBSD came out? The idea is to make sure that RELEASE can be shipped with installation media (CD, DVD) for offline use which requires ports mostly to be tested and working in some specific state, and then the packages (those you can access on the installation media) are generated from them. It's handy for systems that do not have Internet access to install software off-line. It happened all the time and after update (if you update or not) there are so many ports for updating. In case for very long waiting for version 9.1 will be thousands of them. That could probably be. Most users who have Internet access and run servers (and also home systems) will tend to update the OS beyond RELEASE and also do so with the ports collection, or alternatively also use pkg_add -r from the Latest/ directory instead of RELEASE (which _always_ contains the ports generated from the frozen ports tree). Thank you very much. BTW: packages are almost all the time outdated. Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: before new version
On Sat, 3 Nov 2012 12:25:12 -0500, ajtiM wrote: On Saturday 03 November 2012 12:18:35 Polytropon wrote: On Sat, 3 Nov 2012 11:23:12 -0500, ajtiM wrote: Hi! Could someone explain, please why ports should be frozen before a new version of FreeBSD came out? The idea is to make sure that RELEASE can be shipped with installation media (CD, DVD) for offline use which requires ports mostly to be tested and working in some specific state, and then the packages (those you can access on the installation media) are generated from them. It's handy for systems that do not have Internet access to install software off-line. It happened all the time and after update (if you update or not) there are so many ports for updating. In case for very long waiting for version 9.1 will be thousands of them. That could probably be. Most users who have Internet access and run servers (and also home systems) will tend to update the OS beyond RELEASE and also do so with the ports collection, or alternatively also use pkg_add -r from the Latest/ directory instead of RELEASE (which _always_ contains the ports generated from the frozen ports tree). Thank you very much. BTW: packages are almost all the time outdated. The packages in the RELEASE directory and on the installation media meet the frozen ports tree (frozen _prior_ to the release date), so yes, they are a bit outdated, but they are considered mostly stable and usable when in use with what is distributed. On the server, both _those_ packages _and_ those in Latest/ (which are periodically built from the advancing ports tree after the release date) are often considered not _that_ current as if you would use CVS or SVN to obtain the bleeding edge latest ports tree and build from source. So yes, you could say what you said. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: before new version
On Saturday 03 November 2012 14:11:22 you wrote: BTW: packages are almost all the time outdated. The packages in the RELEASE directory and on the installation media meet the frozen ports tree (frozen _prior_ to the release date), so yes, they are a bit outdated, but they are considered mostly stable and usable when in use with what is distributed. On the server, both _those_ packages _and_ those in Latest/ (which are periodically built from the advancing ports tree after the release date) are often considered not _that_ current as if you would use CVS or SVN to obtain the bleeding edge latest ports tree and build from source. I didn't complain about bleeding edge sofware which we anywhere don't have (Gimp, Xorg, LibreOffice and all dependencies for those applications and more and more which I don't use and I don't need) but I complain about freezing ports too early before new release came out and after that rebuilt 5000 ports for example just because png new version is coming out. Or am I wrong? So yes, you could say what you said. :-) Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
