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 8FA4598D3 for ; Wed, 8 Feb 2012 11:29:52 +0000 (UTC) Received: (qmail 31131 invoked by uid 500); 8 Feb 2012 11:29:52 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 31061 invoked by uid 500); 8 Feb 2012 11:29:51 -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 31053 invoked by uid 99); 8 Feb 2012 11:29:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Feb 2012 11:29:51 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jogischmidt@googlemail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Feb 2012 11:29:45 +0000 Received: by bke17 with SMTP id 17so354761bke.6 for ; Wed, 08 Feb 2012 03:29:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=BVM5ulPt1IpDhjR+V867onMrcmq9AtuzoaxCk8KEsWA=; b=bZ7DGbWplgicjoetDMPLYzP1pjvj2us3tFyEYqB/siGgdufIO9NrMindepE9V4Hv00 DfEzFxqKcMHQTA4cYtSQ2ADCSO3VmdFCsicOFJqiN47yFSZdAjIytpOKH7o5bxC0XRa4 IuA3ITBVFU+jLnniNs4cLwpRjPolBZSG8GLas= Received: by 10.204.129.71 with SMTP id n7mr11867390bks.91.1328700564157; Wed, 08 Feb 2012 03:29:24 -0800 (PST) Received: from [9.155.131.21] (deibp9eh1--blueice3n2.emea.ibm.com. [195.212.29.180]) by mx.google.com with ESMTPS id cz3sm3569854bkb.3.2012.02.08.03.29.23 (version=SSLv3 cipher=OTHER); Wed, 08 Feb 2012 03:29:23 -0800 (PST) Message-ID: <4F325C92.8060509@googlemail.com> Date: Wed, 08 Feb 2012 12:29:22 +0100 From: =?UTF-8?B?SsO8cmdlbiBTY2htaWR0?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [RELEASE]: source release script References: <4F30028C.80001@googlemail.com> <4F30E204.3010701@googlemail.com> In-Reply-To: <4F30E204.3010701@googlemail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi, I forgot yesterday to follow up on this a little bit. I did some further tests and have figured out that ant doesn't do a bad job here. I added targets for creating a zip, tar.gz and tar.bz2 and tested them independently. I did the same test native with zip and tar (on a MacOS system of course) on a directory aoo3.4 containing the relevant files (unzipped the ant created zip file ;-)) Time native: aoo-3.4.zip -> 2min 5sec aoo-3.4.tar.gz -> 4min 17sec aoo-3.4.tar.bz2 -> 9min 20sec Time with ant: aoo-3.4.zip -> 2min 46sec aoo-3.4.tar.gz -> ~4min aoo-3.4.tar.bz2 -> ~10min All 3 output files together with ant takes 14min 28sec The ant script creates one tar and used it for both zip files. Probably the time will be varying on the different platforms but the difference is not huge and I will continue with the ant approach. I have to do a little bit more minor things. File sizes by the way are: aoo-3.4.zip -> ~382 MB aoo-3.4.tar.gz -> ~330MB aoo-3.4.tar.bz2 -> ~260MB I can probably add some signing targets to automate some more things... I have to read the docu for managing releases again. Juergen On 2/7/12 9:34 AM, Jürgen Schmidt wrote: > On 2/6/12 7:22 PM, Rob Weir wrote: >> 2012/2/6 Jürgen Schmidt: >>> Hi, >>> >>> I am currently work on a script to package a source release zip, tar.gz >>> file. >>> >>> The idea is to do it later as part of our build bot builds and without >>> copying files into a tmp directory or so to reflect the final directory >>> structure. >>> >>> At the moment I am playing with an ant script that allows me to zip the >>> necessary directories with an exclude list and to prefix everything >>> with a >>> configurable directory name (e.g aoo-3.4). And it allows me to copy some >>> files like the main/NOTICE file into the new root directory. >>> >> >> Is this able to ignore all the hidden .svn folders? > yes > >> >>> The structure can look like >>> >>> aoo-3.4/NOTICE >>> aoo-3.4/README >>> aoo-3.4/LICNESE >>> aoo-3.4/... >>> aoo-3.4/main/... >>> aoo-3.4/extras/... >>> aoo-3.4/ext_libraries/... >>> >>> The nice thing with ant is that I can easy convert a generated zip >>> file into >>> a tar.gz file. But ok that takes some time where as creating the zip >>> file >>> was quite fast. >>> >>> Does anybody has a better idea how to do that without copying all the >>> files >>> in a final directory structure or checking out the files into a target >>> directory for example aoo3.4. >>> >> >> "svn export" will bring down the files without the .svn tracking >> folders. But that is still a separate download. >> >> I wonder if ant is jut calling java.io.zip stuff to do the archiving? >> If so, it might be a lot faster to call a native zip utility. > I don't know but creating the zip file only was ok (2 minutes and 46 > seconds). The conversion of the zip into tar.gz was incredible slow. > It's no option. > > zipping the unpacked aoo-3.4 directory again takes ~2 minutes. But here > we need have to export the sources again in the final directory or copy > everything first into the final directory structure. > > I will do some further test creating tar.gz, tar.bz2 directly. If it's > comparable with creating the zip I would say ant is fine for creating > the src releases. We can simply add a further target for the build bots. > >> >> Question: if we do ZIP on Windows, will it preserve the executable >> bits on files? If not, maybe we want to create the source package >> only from the Linux buildbot and never on the others. > > I have to check it, don't know for sure. But I would say that creating > the src release on Linux should be enough. > > Juergen >