Bug 17948 - update port: x11-wm/sapphire to 0.14.2
Summary: update port: x11-wm/sapphire to 0.14.2
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-04-12 13:30 UTC by Trevor Johnson
Modified: 2000-04-30 22:22 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Trevor Johnson 2000-04-12 13:30:00 UTC
- update to latest sapphire
- install most themes from sapphire Web site
- PORTNAME/PORTVERSION conformance
- all patches in one file, to save inodes
- new pkg/MESSAGE

Thanks to Kato Tsuguru for doing much of the work on this update.

Fix: 

http://jpj.net/~trevor/freebsd/ports/sapphire.shar
MD5 (sapphire.shar) = 61a9133ef02e405e9dc173f87cac0a15
How-To-Repeat: N/A
Comment 1 sprice 2000-04-17 17:19:33 UTC
---------- Forwarded message ----------
Date: Sun, 16 Apr 2000 15:32:20 -0400 (EDT)
From: Trevor Johnson <trevor@jpj.net>
To: gnats-admin@FreeBSD.org, freebsd-ports@FreeBSD.org
Cc: KATO Tsuguru <tkato@prontomail.ne.jp>
Subject: Re: ports/17948: update port:  x11-wm/sapphire to 0.14.2

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 <obrien@FreeBSD.ORG>
Reply-To: freebsd-ports@FreeBSD.ORG
To: Trevor Johnson <trevor@jpj.net>
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)
Comment 2 Steve Price freebsd_committer freebsd_triage 2000-04-30 22:20:26 UTC
State Changed
From-To: open->closed

Update committed, thanks!