--===============1235880600==
Content-Type: multipart/signed;
boundary="nextPart6496399.RYz3NFtYVr";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart6496399.RYz3NFtYVr
Content-Type: text/plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday, 12. July 2005 19:57, Thomas Baumgart wrote:
> Hi all,
>
> on Tuesday 12 July 2005 09:54, Karim Ryde wrote:
> > Hi Jakob!
> >
> > I found the easiest way to create a release tarball is cvs export, run
> > "make Makefile.cvs", delete the newly created dir and files, then tar
> > everything.
>
> I do a 'make distcheck' which packages everything together in a tar.gz
> archive and even checks that it compiles and installs.

A lot of kde application tarballs out there has inconsistent timestamps on=
=20
top-level configure.in.in or Makefile.am or cvs.sh or whatever, causing the=
=20
buildmagic to try and run autotools again when you run make after configure=
-=20
very annoying for packagers, let me tell you.

Perhaps one of the release-gurus (coolo!) could comment on the definitive w=
ay=20
to of rolling a release tarball.

=2D-=20
,_, | Michael Nottebrock | lofi@freebsd.org
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org

--nextPart6496399.RYz3NFtYVr
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQBC1ArVXhc68WspdLARAqnNAJ9GyGf3SpXRtgyrKmoLjz 7y8ZChsACfSt7D
a380ZpZ8d2dir6jXuCzZz3g=
=5SDZ
-----END PGP SIGNATURE-----

--nextPart6496399.RYz3NFtYVr--

--===============1235880600==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscrib=
e <<

--===============1235880600==--