From owner-freebsd-ports Mon Aug 2 18:47:36 1999 Delivered-To: freebsd-ports@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 7DCD214F1D for ; Mon, 2 Aug 1999 18:47:22 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial8-246.netcologne.de [195.14.235.246]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id DAA29584; Tue, 3 Aug 1999 03:47:13 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id DAA00881; Tue, 3 Aug 1999 03:45:28 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Tue, 3 Aug 1999 03:45:28 +0200 (CEST) Message-Id: <199908030145.DAA00881@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: vanderh@ecf.utoronto.ca Cc: freebsd-ports@freebsd.org In-reply-to: <19990802114353.D14922@mad> (message from Tim Vanderhoek on Mon, 2 Aug 1999 11:43:53 -0400) Subject: Re: 2nd level patching Reply-To: van.woerkom@netcologne.de References: <199908021053.DAA25890@freeamp.org> <19990802114353.D14922@mad> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Do you mean you had to apply your own patches to Mesa? > > If so, just put those patches in Mesa3/patches and name them as > "patch-zz", "patcy-zy", etc. cvsup won't touch them and they > shouldn't get overwritten unless someone does something dumb. That is a solution that would just fine for my personal modifications. No my problem is how to create variations of larger ports that should go into the official ports tree. Example: I want a Mesa 3.0 lib with software rendering and another one with hardware rendering. Or even a third one that has been optimized for AMD 3d Now instruction set. How to organize this best? Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message