From owner-freebsd-questions@FreeBSD.ORG Sun Sep 12 15:46:58 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE05A106566B for ; Sun, 12 Sep 2010 15:46:57 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 793508FC15 for ; Sun, 12 Sep 2010 15:46:57 +0000 (UTC) Received: by ewy4 with SMTP id 4so2806263ewy.13 for ; Sun, 12 Sep 2010 08:46:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=0mB2vy9NXObRxFZSMcZ4sRtLHO5+i/cVuVXphUXKxoc=; b=VNU5q/zGEQUnWR+4cycL6RYLfllaZuOmwab3g+awt/o4spR9Efxahe5qeBt1mdCUE6 HKdScSpkHvophT5RK+a0MNoeY4r0gjrRRVyu27CYpDCFHsyZc1FSQaW9hPIE1Z6jHFUk R+Uj9QFZPFEPSNU81btu3wT9CC9jrflWqVAcE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=O31KBHiLlFdd35da1oBkK/F6AIlARJ7L4KJapqqj8h57YgQ3PmvNGMdNvbFCFFvNYk UmMt8vdzmReFuZDYwY6wwRL0MEq0gmuvammYsvgpBTQj8ayVVSqKpQhVX6LDTncUZd0l cBN82gl+41PerOQoWAKT25LNldIVdcyfil6JA= Received: by 10.14.45.66 with SMTP id o42mr1986248eeb.10.1284306414485; Sun, 12 Sep 2010 08:46:54 -0700 (PDT) Received: from [172.16.0.4] ([212.156.209.87]) by mx.google.com with ESMTPS id v8sm7620303eeh.8.2010.09.12.08.46.53 (version=SSLv3 cipher=RC4-MD5); Sun, 12 Sep 2010 08:46:53 -0700 (PDT) Message-ID: <4C8CF5EC.80206@gmail.com> Date: Sun, 12 Sep 2010 18:46:52 +0300 From: Kaya Saman User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4C8C0110.20801@gmail.com> <4C8CBADC.3070904@gmail.com> <4C8CDAAD.2070606@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Upgrading packages - portupgrade confusion X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Sep 2010 15:46:58 -0000 Thanks Warren and Michael! :-) On Sun, 12 Sep 2010, Kaya Saman wrote: > The thing I don't quite understand though is that if the ports tree > gets refreshed, do the packages get upgraded or will I need to rebuild > them?? The ports tree is just build instructions, so updating it doesn't update any installed applications. It does let you use a program to see which installed applications need to be updated, like pkg_version or portversion. Here's a document I've been working on lately about upgrading ports. I'm not sure it's really there yet, but it covers the basics: http://www.wonkity.com/~wblock/docs/html/portupgrade.html Yep I kinda figured that before even posting and also I knew the difference between packages built by pkg_add and compiling fresh from ports since I've done a few BSD builds now but the really iffy thing was a: communication - which let me down not explaining myself properly and b: confusion of how to update On 09/12/2010 05:36 PM, Michael Powell wrote: > [...] > Yes. A package is just a port that someone has compiled into a pre-built > binary package for use with pkg_add. These binary packages are placed on ftp > servers where pkg_add may download from and install. > > A port is just you doing the compiling locally yourself using the ports > system. The installed result is the same, except for one thing. When a > package is built some build options may have been selected as defaults while > others were excluded. When you build the port locally you have complete > control over all options. > > Ditto :-) >> "portupgrade -a" or "portmanager -u" depending on what application you >> are using. Switching between multiple port maintenance applications is >> not the worse thing you could do; however, I would not recommend it as >> an everyday occurrence. >> >> >> Ok so "portupgrade -a" upgrades all ports according to the manual. >> >> > [snip] > > >> Ok, so if I understand correctly now is that the csup command refreshes >> the ports tree while portupgrade upgrades the actual port itself.... >> > Update the ports tree first! csup -L 2 ports<- this file "ports" is a > supfile. An example of a supfile was included in a previous mail. More > detailed info in the Handbook. > This clarifies, I can't believe what's wrong with me today as I seem to not be thinking :-( I picked this up the first time round on a really good production build that I made and now I lost all that knowledge.... oh well working with MS can do that to you I guess?? > > > [...] > Another tip: Whenever there are situations which can get sticky most of the > time notes are placed into a file containing instructions on how to deal > with the problem. Get into the habit of always reading the UPDATING file > located in /usr/ports so you will know about these *before* updating. > > [snip] > > This is really great advise as I'm kinda in the process of developing documentation myself similar to Warren: http://wiki.optiplex-networks.com/xwiki/bin/view/FreeBSD/ Luckily I build all my systems in jails so is easily managed and doesn't blow up the whole system, however I do share the ports tree throughout all jails and the base install meaning that things get simplified although it can have its own problems such as version inconsistencies etc... {{PS. this is also due to the fact that I only one available production system and can't afford to get more although soon I hope to one day}} Thanks so much guys and sorry for being so noobish these last 2 days, just sorry you all had to put up with it!! :-) Anyway best regards to all and hopefully mail along side you guys helping out others some sunny day in the future :-D Kaya