Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFABF9CF8 for ; Mon, 30 Apr 2012 18:48:25 +0000 (UTC) Received: (qmail 98536 invoked by uid 500); 30 Apr 2012 18:48:25 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 98371 invoked by uid 500); 30 Apr 2012 18:48:25 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 98363 invoked by uid 99); 30 Apr 2012 18:48:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2012 18:48:25 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of marcus.mail@wtnet.de designates 213.209.103.13 as permitted sender) Received: from [213.209.103.13] (HELO smtp3.wtnet.de) (213.209.103.13) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2012 18:48:16 +0000 X-WT-Originating-IP: 84.46.106.163 Received: from f9.linux (pop8-672.catv.wtnet.de [84.46.106.163]) (authenticated bits=0) by smtp3.wtnet.de (8.14.4/8.14.4) with ESMTP id q3UIltM7007968 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Mon, 30 Apr 2012 20:47:55 +0200 Message-ID: <4F9EDE5B.6080608@wtnet.de> Date: Mon, 30 Apr 2012 20:47:55 +0200 From: "Marcus (OOo)" User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [RELEASE]: proposed directory structure on dist References: <4F9A860F.1070800@googlemail.com> <4F9AEA44.7020706@googlemail.com> <4F9AEF84.1090203@wtnet.de> <4F9AF7D4.4030708@wtnet.de> <4F9AFCE7.4040303@gmail.com> <4F9E3B4C.9040403@googlemail.com>

In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Am 04/30/2012 07:00 PM, schrieb Rob Weir: > On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenk wrote: > > > >> Right now I have the DL friendly script setup to only use SF...which is >> setup in the "old" way. I don't think we'll be usign Apache for pre-build >> client downloads. >> >> So, I have a question -- who will be setting up the SF packs and will they >> just stick with the current structure on that system for DLs -- >> >> i.e. >> >> /files/stable// >> >> >> and >> >> /files/localized/// >> >> I'm hoping the answer is "YES". >> > > Whatever we do, let's try to get a directory schem that works now and > for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. This is not > something where it will be easier to clean up later. Honestly spoken, I don't know if this will work. Of course it could be easy and fast to think about a directory structure that will work also for a AOO 5.0 release. However, I doubt that we will have the time to make the DL logic work this way, too. As I've no idea how close we are from the first public download of AOO 3.4 I wouldn't do bigger changes now. > Thinking ahead, what do we do when we have a new release, like a > 3.4.1? And what can we do now to make that future less painful? The DL logic for 3.4.1 can be the same as for 3.4.0. There shouldn't be big changes. For further releases see above. Juergen is already OK to setup the structure like it was in the old project, so that the need changes to the DL logic is minimal. To setup a new structure that makes maybe more sense can be done later for a release after 3.4.x. my 2 ct Marcus