Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 1998 08:14:49 +0300 (MSK)
From:      =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru>
To:        ports@FreeBSD.ORG
Cc:        asami@cs.berkeley.edu, committers@FreeBSD.ORG, gpalmer@FreeBSD.ORG, perhaps@yes.no, peter@netplex.com.au
Subject:   Ports system possible fixups list (PLEASE READ)
Message-ID:  <Pine.BSF.3.96.980120080459.257A-100000@ache.relcom.ru>
In-Reply-To: <Pine.BSF.3.96.980119090210.16547A-100000@lsd.relcom.eu.net>

next in thread | previous in thread | raw e-mail | index | archive | help
At this moment I see following variants to compensate patch returning to
FreeBSD 2.1.0R behaviour (besides nonsense back out suggested by many).

1) Build separate /usr/bin/broken_patch especially for ports system
(with one-line change in bsd.port.mk)
 
2) Scan all Index: patches in ports tree to replace ---/*** lines
with correct ones.

I find following ports which use Index: lines
 
 	kinput2-canna+sj3+wnn, kinput2-canna+wnn, kinput2-sj3+wnn,
 	kinput2-wnn, modula-3-lib, 
 	modula-3-socks, virtualpager, tkdesk, rtptools, rdist6, sup
 
 Really not so many! I not check yet how many from them have bogus
 ---/*** lines. 
 
3) Make sed filter to detect patches with broken Index: and convert
 them on the fly.

Anything else?

-- 
Andrey A. Chernov
<ache@nietzsche.net>
http://www.nagual.pp.ru/~ache/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980120080459.257A-100000>