[Bug 453772] Review Request: perl-Gtk2-ImageView - Perl bindings to the GtkImageView image viewer widget

[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: perl-Gtk2-ImageView - Perl bindings to the GtkImageView image viewer widget


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





------- Additional Comments From jrowens.fedora at ghiapet.net  2008-07-02 18:25 EST -------
Of course it failed to build for you; I said right above, "I had to update
gtkimageview to 1.6.1 (currently at 1.5.0; the Gtk2::ImageView docs say 1.6.0 is
minimum) to build the perl package."  That's why I provided those extra links;
you have to build gtkimage-1.6.1, make it available to your build system, then
build perl-Gtk2-ImageView, make it available, then build gscan2pdf (the point of
the whole exercise).

Yes, I was in the middle of reading a number of the package review pages while I
did this, and got to the maintainer page somewhere along the line, I think.  I'm
not sure I'd be a good maintainer for this in the long run, though; I know perl
pretty well, but neither c nor the .xs stuff that binds them together.  I just
saw that this was needed, so I thought I'd get the ball rolling.  I would think
a maintainer should be qualified to audit the changes in updates to the code in
the package s/he maintains?  I'm not.  If, on the other hand, all you really
need to know is the packaging process, I could be up for that.

To be quite honest, I was wondering why he had it on that webfactional.com page
instead of CPAN, but I didn't think to check on CPAN too.  1.6.1-2 coming right up!

I have contacted Nils Philippsen, maintainer of gtkimageview, about this.  He
seems willing to push the gtkimageview-1.6.[01] update soon.  Should another bug
be opened for that, or is the suggestion enough?

-- 
Configure bugmail: https://bugzilla.redhat.com/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.