[Bug 206814] Review Request: hugin - Frontend for Panorama Tools, similar to PTAssembler, PTGui or Open for Windows

[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: hugin - Frontend for Panorama Tools, similar to PTAssembler, PTGui or Open for Windows


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


paul at all-the-johnsons.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
OtherBugsDependingO|163776                      |163778
              nThis|                            |




------- Additional Comments From paul at all-the-johnsons.co.uk  2006-09-17 06:12 EST -------
BuildRequires: libpano12-devel > 2.8.3 zlib-devel libtiff-devel libjpeg-devel
libpng-devel gettext-devel gcc-c++
BuildRequires: libstdc++-devel wxGTK-devel >= 2.6.0 boost-devel gtk+-devel
glib2-devel

You don't need gcc-c++ or libstdc++-devel really. Is there a reason for using
the old gtk instead of gtk2?

# autopanog.exe is a mono app

In which case you need the BRs for mono - at least mono-devel and remember, if a
mono app is being included, you're limited to FC5 and FC6. Currently, you also
need a hack as FC6 mono is architecture agnostic (it get's things right!) and
will probably need to fix things in the source. Let me know if you need a hand
with it as mono can be a pain at times!

%build
%configure
make

Any reason for not using smp_mflags? If it fails, you need to include a comment
as to why

%{_datadir}/locale/*/LC_MESSAGES/hugin.mo
%{_datadir}/locale/*/LC_MESSAGES/nona_gui.mo

These are handled incorrectly. 

Some of the time with findlang, you need to use something other than %{name}.
For example, in gnome-build, I use %find_lang gbf-1

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.