From owner-freebsd-ports Sun Apr 16 12:32:27 2000 Delivered-To: freebsd-ports@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 5949137B856; Sun, 16 Apr 2000 12:32:23 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e3GJWK518298; Sun, 16 Apr 2000 15:32:21 -0400 (EDT) Date: Sun, 16 Apr 2000 15:32:20 -0400 (EDT) From: Trevor Johnson To: gnats-admin@FreeBSD.org, freebsd-ports@FreeBSD.org Cc: KATO Tsuguru Subject: Re: ports/17948: update port: x11-wm/sapphire to 0.14.2 In-Reply-To: <200004121230.FAA58120@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've made a couple of further changes to this update. It now conforms to section 4.4.15.11 in the Handbook ("one source file per patch file"). However, if it can be allowed, I'd prefer patch-ae through patch-ao (the ones that patch the themes) to be concatenated into a single patch, but patch-aa through patch-ad (the ones that patch the code) kept as separate files, as in Kato Tsuguru's example. I thought this was okay because of the appended e-mail from David O'Brien. The other change is the use of xsetbg, suggested by Kato Tsuguru. This is essentially a succinct way of doing "xloadimage -onroot -quiet". On FreeBSD, xsetbg is mentioned in the xloadimage man page as well as the xli man page, but is only installed by the xli port. Accordingly the updated sapphire port depends on xli. http://jpj.net/~trevor/freebsd/ports/sapphire.shar MD5 (sapphire.shar) = c9461bde61822f2cb72c8a497c472673 __ Trevor Johnson Date: Mon, 14 Feb 2000 18:39:59 -0800 From: David O'Brien Reply-To: freebsd-ports@FreeBSD.ORG To: Trevor Johnson Cc: freebsd-ports@FreeBSD.ORG Subject: Re: /usr/ports/ too big? On Mon, Feb 14, 2000 at 05:43:24PM -0500, Trevor Johnson wrote: > I like Jeremy's suggestions. I don't know whether it's just me, but I > find it easier to do something like: ... > $ diff -ruN foo-1.0.orig/ foo-1.0/>foo-1.0.diff A port's maintainer has always been able to get away with this. > (11 inodes) to: > /usr/ports/textproc/diffstat$ find . > ./diffstat.diff However this is too unwieldy for some of the larger ports I maintain. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message