[mono-packagers] Generating "release" tarballs from SVN

[Jo Shields]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi,

In Debian and Ubuntu, we have imminent freezes, and have opted to go
for the long-term-support mono-2-4 branch for these long-term-support
distros. We're pretty much in need of a 2.4.4 release for various
reasons, and with no sign of such a release on the horizon, we're
probably going to have to go for a SVN snapshot rather than an
official tarball.

I'm relatively comfortable with "make dist" in general, but it's not
entirely clear to me how to deal with the mini/mono situation:

/tmp/monohell/mono-2-4/mono/libtool: line 8874:
/tmp/monohell/mono-2-4/mono/mono/mini/mono: No such file or directory
/tmp/monohell/mono-2-4/mono/libtool: line 8874: exec:
/tmp/monohell/mono-2-4/mono/mono/mini/mono: cannot execute: No such
file or directory

I know there's a script to download the "latest" mini, but I doubt
that's what goes into the release tarballs. What's the correct
procedure here?

Thanks.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
iQEcBAEBAgAGBQJLeb6TAAoJEMkPnLkOH60M02sH+gIVLnQpl63j5dqrMl5MUGlk
2pvd+QY5SDCu3/+hk6FSSvWcEekxG2hWIb2rCBU/T44xqGUwsK8RVZwBwkQ8hbKM
so3auFwZ4EhxWbgklthvbKvWu9EYAleQq+er/cGCzJwazeuxLOKBgHyNyOMFbPgN
KwbeVMYStU51pyTftISnbXvpVK++Y6kqOzj92X/R3acocDjbU5S0U1e04Nz+bVDp
bS2+yR/kBSFJ2NNL92y2BXbfSSVoYE8a+ZIa1PPqcc5czD4FS4C2FPR2UM8kv0Hg
JS4cM1voLMXV5Q4B7uS9XPPxo4PWkd7JxUN9feMHoeMl2Z8i6KR7TTN20UiDueM=
=CBOK
-----END PGP SIGNATURE-----