Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 98061 invoked by uid 500); 28 Oct 2002 15:27:32 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 98050 invoked from network); 28 Oct 2002 15:27:32 -0000 Content-Type: text/plain; charset="us-ascii" From: Torsten Curdt Organization: dff internet & medien To: cocoon-dev@xml.apache.org Subject: scratchpad blocks Date: Mon, 28 Oct 2002 16:29:52 +0100 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200210281629.52672.tcurdt@dff.st> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N What about having blocks inside the scratchpad? I just wanted to package = the=20 precept stuff but it should not go into the maintrunk. so... I think scratchpad blocks would unify the pattern of creating new stuff..= =2E it=20 also would be a piece of cake to move things out of the scratchpad then.=20 On the other hand we could also just create blocks and mark them appropri= atly=20 and exclude them from the standard build. So we could: 1) leave everything like it is :-( 2) have another blocks directory under scratchpad 3) have a single blocks directory and mark and exclude scratchpad stuff What do you guys think? -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org