DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:cc:in-reply-to:references:content-type:date
         :message-id:mime-version:x-mailer:content-transfer-encoding;
        b=aQp5qtcZO880UWa++ggiTL6lqtGUQv+bWzzBnZ65cPVFA7995oxk7+HkqROLeV0xNB
         Qo6UBOnD4r/5fCcCzKyeWMb87LdwjbHw9bYKiTxqjfcgrCa4sn8k/jNJlqOhPEb5pSPq
         NioZqjP4WG1F1WNxjsHKdipbYu+nQ+lGql5zk=
Subject: Re: [alpine-devel] How best to track packages changes?
From: Natanael Copa <natanael.copa@gmail.com>
To: Mark Constable <markc@renta.net>
Cc: alpine-devel@lists.alpinelinux.org
In-Reply-To: <4A779067.4070501@renta.net>
References: <4A779067.4070501@renta.net>
Content-Type: text/plain
Date: Tue, 04 Aug 2009 07:56:38 +0200
Message-Id: <1249365398.12941.39.camel@localhost.localdomain>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2009-08-04 at 11:35 +1000, Mark Constable wrote:
> So this morning I did this and I'm wondering what is the best
> way to see exactly what changes went into these updates?
> 
> # apk add -u alpine-sdk
> Upgrading uclibc (0.9.30.1-r13 -> 0.9.30.1-r14)
> Upgrading abuild (2.0_rc3-r1 -> 2.0_rc4-r0)
> Upgrading uclibc-dev (0.9.30.1-r13 -> 0.9.30.1-r14)
> Upgrading busybox (1.14.2-r2 -> 1.14.3-r0)
> Executing busybox-1.14.3-r0.post-upgrade
> OK: 134 packages, 471 dirs, 7051 files
> 

I suppose the git is the best way to see exactly what happened:
http://git.alpinelinux.org/cgit/aports/log/

btw. abuild-2.0_rc4 introduces -d to disable dependency tracing, as we
talked about ;)

-nc



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---