From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9309 invoked by uid 1002); 14 Jun 2003 18:31:59 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 29946 invoked from network); 14 Jun 2003 18:31:57 -0000 From: Todd Berman Reply-To: tberman@gentoo.org To: gentoo-dev@gentoo.org In-Reply-To: <200306141957.01121.rcm@sasaska.net> References: <200306141957.01121.rcm@sasaska.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Dql+ajuaAvAniytuhS0z" Message-Id: <1055615283.21062.7.camel@phaze> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 14 Jun 2003 14:28:03 -0400 Subject: Re: [gentoo-dev] Improving Portage Watch script X-Archives-Salt: 1cefca95-9e18-4274-8be9-13e6cd2479be X-Archives-Hash: 89299cc31c3a802c169efb9debb92fc8 --=-Dql+ajuaAvAniytuhS0z Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2003-06-14 at 13:57, Rafael Cordones Marcos wrote: > Hi, >=20 > I want to improve the current script that generates the Portage Watch sec= tion=20 > in GWN. The two problems I am focusing right now are: >=20 > 1.- Listing the USE variables that were added or removed since a given da= te. >=20 > I have been looking around Portage but I cannot find any ChangeLog where = I can=20 > get this info. A /usr/portage/profiles/use.desc ChangeLog would be perfec= t! > 2.- Differentiating between updated packages and new packages >=20 > For this I think I can manage by looking at the last entry of the ChangeL= og=20 > file and extracting the date from it. Example: > /usr/portage/app-cdr/k3b/ChangeLog >=20 > > [...] > *k3b-0.5.1 (1 Feb 2002) >=20 > 1 Feb 2002; G.Bevin ChangeLog : >=20 > [...] > >=20 > One more thing, are ChangeLog files in packages automagically generated f= rom=20 > CVS or are they hand-edited by developers? If they are hand edited then I= am=20 > going to find errors in the format. I mean that humans commit errors and,= for=20 > instance, some dev can forget to write the "*" at the begining of a Chang= eLog=20 > entry! The Changelogs are created by a small script called echangelog, so its pretty easy to handle :) --Todd --=-Dql+ajuaAvAniytuhS0z Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA+62kzPaCtt9MQLlARAloZAJ9+AvqEXyY1OOuGSKa88/MEZWPL/ACeOzik BhshmAfu1OkeqUPuv8iUoAQ= =TIkA -----END PGP SIGNATURE----- --=-Dql+ajuaAvAniytuhS0z--