Commit 484cc132 authored by Cyrille Chepelov's avatar Cyrille Chepelov

removed macro nesting related to libpng.h, which was causing some problems

	* configure.in: removed macro nesting related to libpng.h, which
	was causing some problems on some systems (like mine, which made
	the snapshots bad).

        * RELEASE-PROCESS: added James' notes on how to properly make the
	tarball.
parent 1390fb9d
2002-05-13 Cyrille Chepelov <cyrille@chepelov.org>
* RELEASE-PROCESS: added James' notes on how to properly make the
tarball.
* configure.in: removed macro nesting related to libpng.h, which
was causing some problems on some systems (like mine, which made
the snapshots bad).
2002-05-13 Steffen Macke <sdteffen@web.de>
* AUTHORS:
......
......@@ -32,6 +32,8 @@ When a new version is about to be released:
the Bugzilla, however it is encouraged that bug reports are made
directly (or simultaneously) to the mailing list.
Please see the section below on how to make a tarball (yes, please do).
3a) if a release-critical bug happens before D+10 (say, at D+n), the
release process is paused until the bug is fixed and a new release
candidate tarball $VERSION-pre2 is re-made. Go to either step 3a or
......@@ -45,7 +47,9 @@ When a new version is about to be released:
rejected as INVALID).
4) once the new release is complete and uploaded, announcements on
freshmeat and the dia web site are made.
freshmeat, the dia web site, the dia mailing list,
gnome-announce-list@gnome.org and maybe a gnotices story
(news.gnome.org) are made.
5) the CVS HEAD freeze is lifted one week /after/ the release is
generally available, unless a release critical bug is discovered in
......@@ -53,6 +57,24 @@ When a new version is about to be released:
released and announced as soon as possible (extending the one-week
delay on the CVS HEAD thaw).
How to make a tarball
---------------------
1. make sure you have up to date build tools installed on the system.
Libtool is an important one, as new releases add support for new
platforms.
2. make sure "make distcheck" runs to completion. With automake >=
1.5, the checks also make sure "make uninstall" removes all files
that got installed.
3. check to see if the tarball builds in normal and --enable-gnome
modes (this task should disapear with the move to 2.0; there is no
reason to have separate dialog and menu code).
4. Upload to ftp.gnome.org. This is basically just scp'ing the
tarball to widget.gnome.org, then running a command like
"install-module --package dia-0.90.tar.gz --old
dia-0.88.1.tar.gz", which will create bz2 tarballs, diffs to the
previous version, and signal the ftp mirrors (currently just
ftp.gnome.org and planetmirror.com) to synchronise.
Issues to solve
---------------
......
......@@ -205,8 +205,8 @@ dnl libpng
dnl
png_ok=no
AC_CHECK_LIB(png, png_read_info,
AC_CHECK_HEADER(png.h, png_ok=yes, png_ok=no),png_ok=no, -lz -lm)
AC_CHECK_HEADER(png.h, png_ok=yes, png_ok=no)
AC_CHECK_LIB(png, png_read_info, ,png_ok=no, -lz -lm)
if test "$png_ok" = yes; then
AC_MSG_CHECKING([for png_structp in png.h])
AC_TRY_COMPILE([#include <png.h>],
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment