Re: new ooo-build workflow for developers and packagerts

--MP_/_B_aLt=GLPVcnkD5YKMe8Gf
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Fri, 10 Sep 2010 20:52:43 +0200
Petr Mladek <[email protected]> wrote:

> Hi,

Hi Petr,

> 2. I think that --with-tag option does not longer make sense. If you
>    want to use another ooo sources, you should use the new
>    --with-source-version option that is more descriptive
> 
>    I am going to remove the --with-tag option

I use that option to build with upstream source tarballs [0].
That is possible with a little hack of mine, attached.

Simply because I do not want to fetch OOo sources via git
and generate tarballs on my own etc since there are tarballs
available already.

Without that option, how am I supposed to use upstream
source tarballs?

	Not at all anymore?

Are there source tarballs for ooo-build I could use instead?
How would I configure that then?

Thank you for any help!


Kind regards,
Hanno


[0] http://download.services.openoffice.org/files/extended/developer/
--MP_/_B_aLt=GLPVcnkD5YKMe8Gf
Content-Type: text/x-patch
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=configure_with-tag.diff

--- configure.in	2010-07-10 18:08:13.696575080 +0200
+++ configure.in	2010-07-10 18:09:08.479575723 +0200
@@ -1609,9 +1609,11 @@
    UPSTREAM_VERSION=3.2.0
 elif test "$with_tag" = "OOO320_m17" ; then
    UPSTREAM_VERSION=3.2.1
+elif test "$with_tag" = "ooo330-m7" ; then
+   UPSTREAM_VERSION="OOO330m7"
 fi
 if test -n "$UPSTREAM_VERSION"; then
-   UPSTREAM_NAME="OOo_${UPSTREAM_VERSION}_src"
+   UPSTREAM_NAME="OOo-Dev_${UPSTREAM_VERSION}_src"
 
    if test "z$with_mirror" != "z" ; then
       SOURCE_TYPE="MIRROR"

--MP_/_B_aLt=GLPVcnkD5YKMe8Gf
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline