Date: Thu, 29 Dec 2011 19:53:25 +0100 From: Walter Alejandro Iglesias <roquesor@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Same version on binary packages and updated ports Message-ID: <20111229185325.GA56404@chancha.local> In-Reply-To: <51AF4F0E-AD5A-4D0A-BC33-4C452B2D1650@mac.com> References: <20111229161611.GA81214@chancha.local> <51AF4F0E-AD5A-4D0A-BC33-4C452B2D1650@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I really appreciate that you all, Jerry, Polytropon and Chuck, took your time to answer me. But I think some of you understood paragraphs like individual-separated statements, that's why you did not fully understand my question (my horrible English helps too :-)). Let's see if I can explain myself. I know that FreeBSD base system and 3rd party are "managed" separately. For RELEASE I meant the ports included in a fresh RELEASE install. The scenario is: what to do after a fresh RELEASE install. Once you updated the ports with 'portsnap fech extract update' you have newer versions at the port tree. Then you can upgrade the already installed software using portupgrade... But compiling! Because, to download *binary* packages, both tools, portupgrade and pkg_add, will download RELEASE, STABLE or CURRENT versions of software depending on what you put in PACKAGESITE variable. So, unless I am missing some portupgrade option-feature, once the port tree is updated I must compile all from source. The opposite leads to dependencies issues. Walter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111229185325.GA56404>