[Bug 176200] Review Request: Mud Magic Client

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: Mud Magic Client


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176200


imlinux at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |imlinux at gmail.com




------- Additional Comments From imlinux at gmail.com  2006-01-25 00:25 EST -------
-Source should be http://dl.sourceforge.net/kyndig/%{name}-%{version}.tar.gz
-Source must be available at dl.sourceforge.net (currently only 1.7 is)
-Change Release: see http://fedoraproject.org/wiki/DistTag
-Duplicate Build Requires:
      glib2-devel provided by gtk2-devel
      pango-devel provided by gtk2-devel
      pkgconfig provided by glib2-devel
      gtk2-devel provided by libglade2-devel
-Inconsistant use of RPM_BUILD_ROOT
-I'd just define version under Version: 
-Don't include dist tag in the change log, version-release is fine

I could not get this to compile on my FC4 machine.  See error below:

--------------------------------------
creating libmxp.la
(cd .libs && rm -f libmxp.la && ln -s ../libmxp.la libmxp.la)
make[2]: *** No rule to make target `../bundled/bundled/pcre/pcre.c', needed by
`pcre.lo'.  Stop.
make[2]: Leaving directory
`/home/IES_CHICAGO/mmcgrath/rpm/BUILD/mudmagic-1.8/bundled'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/IES_CHICAGO/mmcgrath/rpm/BUILD/mudmagic-1.8'
make: *** [all] Error 2
error: Bad exit status from /home/IES_CHICAGO/mmcgrath/rpm/BUILD/rpm-tmp.45059
(%build)
-------------------------------------

Looks like Warren beat me to this but I'll submit it anyway because I too am
learning the packaging guidelines :-D

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.