From owner-cvs-all  Thu Apr  2 06:05:56 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA15551
          for cvs-all-outgoing; Thu, 2 Apr 1998 06:05:56 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15542
          for <cvs-committers@FreeBSD.ORG>; Thu, 2 Apr 1998 06:05:51 -0800 (PST)
          (envelope-from nik@iii.co.uk)
From: nik@iii.co.uk
Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25])
	by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id PAA28503;
	Thu, 2 Apr 1998 15:05:36 +0100 (BST)
Received: (from nik@localhost)
	by carrig.strand.iii.co.uk (8.8.8/8.8.7) id PAA04217;
	Thu, 2 Apr 1998 15:05:19 +0100 (BST)
Message-ID: <19980402150518.05921@iii.co.uk>
Date: Thu, 2 Apr 1998 15:05:18 +0100
To: John Polstra <jdp@polstra.com>
Cc: obrien@NUXI.com, cvs-committers@FreeBSD.ORG
Subject: Re: cvs commit: distrib/cvsup/sup README distrib/cvsup/sup/doc-all releases list.cvs.en distrib/cvsup/sup/www releases list.cvs.en list.cvs.text
References: <19980331193916.63457@nuxi.com> <199804021323.FAA03420@austin.polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85e
In-Reply-To: <199804021323.FAA03420@austin.polstra.com>; from John Polstra on Thu, Apr 02, 1998 at 05:23:27AM -0800
Organization: interactive investor
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

On Thu, Apr 02, 1998 at 05:23:27AM -0800, John Polstra wrote:
> > But we do have say "ports-lang" in addition to "ports-all".  This
> > could also be added to the refuse file.
> >
> > Thus can "doc-all" also be offered in its componates?  These being
> > doc-handbook, doc-faq, doc-ja?
> 
> I don't object in principle.  We'd need "doc-base" too, to pick up
> the Makefile.  I also have been persuaded that subcollections to
> separate out the language-specific parts (e.g., Japanese versions)
> are becoming more important all the time.  

The Handbook DTD migration is about to make this a little more consistent,
since I'm taking the opportunity to create a doc/en hierarchy.

Right now it justs consists of doc/en/handbook and the files in there
(currently unbuildable, since I'm partway through the conversion process).
When the conversion process is complete I'll remove doc/handbook and
start on doc/faq (although there's nothing to stop someone else 
starting on doc/faq in the meantime).

This will (presumably) make things a little easier, since we can then
have 

    doc-all
       doc-base
       doc-en
           doc-en-faq
           doc-en-handbook
       doc-ja
           doc-ja-faq
           doc-ja-handbook

and so on.

Is it possible to use a scheme like this to create meta-collections 
that don't have a 1:1 mapping to the directory structure? For example, a
doc-handbook collection that consisted of doc-en-handbook and 
doc-ja-handbook?

N
-- 
Work: nik@iii.co.uk                       | FreeBSD + Perl + Apache
Rest: nik@nothing-going-on.demon.co.uk    | Remind me again why we need
Play: nik@freebsd.org                     | Microsoft?

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message