From owner-freebsd-ports Thu Dec 4 02:49:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA10910 for ports-outgoing; Thu, 4 Dec 1997 02:49:16 -0800 (PST) (envelope-from owner-freebsd-ports) Received: from silvia.HIP.Berkeley.EDU (ala-ca34-49.ix.netcom.com [207.93.143.177]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA10888 for ; Thu, 4 Dec 1997 02:49:11 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id CAA16348; Thu, 4 Dec 1997 02:49:05 -0800 (PST) Date: Thu, 4 Dec 1997 02:49:05 -0800 (PST) Message-Id: <199712041049.CAA16348@silvia.HIP.Berkeley.EDU> To: bruce@gtcs.com CC: freebsd-ports@freebsd.org In-reply-to: (message from Bruce Gingery on Thu, 4 Dec 1997 02:52:53 -0700 (MST)) Subject: Re: Q: When one dist makes several useful ports? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * and in the future, most likely * Linux * BeOS - PC * and FreeBSD Wow! Run FreeBSD under FreeBSD emulation? Can I run my 1.1 CD again? :) * Would it therefore be best to make *three* portballs out of this? * * 1. Common components * 2. top-end support * 3. minimal-impact * * .. with #2 and #3 both dependent on #1? That sounds cool. Look at editors/mule-common and various mule ports. Basically mule-common is the "common components" part, mule is the "minimal impact" part with hooks to build others, and {chinese,japanese,korean}/mule-* are ones with various options for specific languages and input formats. These are overly complicated because they attempt to share the work/ subdirectory for mule-common and one of the others, but if you are willing to extract and build the ports twice, it should be much easier. Satoshi