Re: new ooo-build workflow for developers and packagerts

--===============1850387077==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="1xJJiECQTZ8+YlWm"
Content-Disposition: inline


--1xJJiECQTZ8+YlWm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 10, 2010 at 08:52:43PM +0200, Petr Mladek <[email protected]> wro=
te:
> There are currently two FIXME's:
>=20
> 1. I think that --with-git=3D/path-to-another-clone-dir should cause
>    that the other clone is used as reference to create the new clone;
>    the new clone still should push directly to freedesktop.
>=20
>    Is this true? Kendy, Thorsten?

I'm not Kendy but yes, since the .git/config of the new repo will be a
symlink to the old one.

>=20
> 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
>=20
>    I am going to remove the --with-tag option

Please don't forget the FIXME about the l10n tarball vs --with-tag.  I
think either cgit should be fixed or it would be nice to release
tarballs of the repos as well, as we discussed on IRC (the later is my
preferred method and IIRC Fridrich and Rene agreed).

Of course I'm not claiming, just wanted to note this. :)

--1xJJiECQTZ8+YlWm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkyKhQAACgkQe81tAgORUJbG3gCfWLfvQ7RF7hcXx6xcvkdMqU0A
3pMAn3HKnBUF+VaRS2fLL6zn0dWhzkXC
=YL6K
-----END PGP SIGNATURE-----

--1xJJiECQTZ8+YlWm--

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