From owner-freebsd-ports Fri Nov 8 16:57: 9 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B32C37B401 for ; Fri, 8 Nov 2002 16:57:07 -0800 (PST) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8029243E77 for ; Fri, 8 Nov 2002 16:57:06 -0800 (PST) (envelope-from babolo@aaz.links.ru) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by aaz.links.ru (8.12.6/8.12.6) with ESMTP id gA90wTDh097872; Sat, 9 Nov 2002 03:58:29 +0300 (MSK) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.12.6/8.12.6/Submit) id gA90wTom097871; Sat, 9 Nov 2002 03:58:29 +0300 (MSK) Message-Id: <200211090058.gA90wTom097871@aaz.links.ru> Subject: Re: general questions about patches ports [nethack] X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <200211081800.59596.timothy@voidnet.com> To: Eric Timme (by way of Eric Timme ) Date: Sat, 9 Nov 2002 03:58:29 +0300 (MSK) From: "."@babolo.ru Cc: freebsd-ports@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [ Charset ISO-8859-1 unsupported, converting... ] > In an effort to get some experience with ports I've been working in my spare > time on making a local entry in the tree that lets you apply a variety of > nethack enhancing, generally accepted patches (namely the hell patch, dump > patch, new toys, and toughvlad patches) using -D appendations to the initial > make command. It builds fine with various patches enabled; however, I had to > modify the original diffs to get everything to apply it an order independent > fashion. Part of this was necessary because I was specifying the files to > use via PATCHFILES and some .if defined() ... .endif branches in the > Makefile, and their application order did matter. > > Anyhow, I got that sorted out, and have been storing my patchfiles on a > remote server and fetching using a PATCH_SITES define, which fetches and > applies seamlessly. > > That brings me to my questions.. > > First, for future reference, is there a way, besides naming patchfiles aa ab > ac etc, to get PATCHFILES, or any similar defines, to apply patches in a user > specifid particular order? > > Second, is there a way to store/bundle optional patches with a port and be > able to include them in the build or not, at your discretion, so that you > don't have to fetch them from third party sites? > > Third, is there even any interest in something like this, or does > conservative BSD philosophy frown on game patches such as these being > included in the ports tree, leaving it to the end user to compile from > scratch and apply patches by hand if they wish enhancement? May be it answers part of your questions: http://free.babolo.ru/patch/ports.Mk.port.mk.patch introduce ${USERPATCHDIR} which is ~/${PATCHDIR} where local patches live and apply after system patches. There my patch tree in http://free.babolo.ru/ports/ which I copy by cvs or wget to any new system I work with. I do not think that there is need some more Mk.port.mk support for retrieve local patches, but I plan to redesign USERPATCHDIR to something LOCAL_SYSTEM_PATCHDIR in such a way, that this variable in /etc/make.conf can be used for any sysadmin in a system. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message