From b044a583716f77bf367789a9038bb1a890177f5c Mon Sep 17 00:00:00 2001
From: Roman Kulik <kuli0020@users.sourceforge.net>
Date: Tue, 13 Sep 2005 17:01:02 +0000
Subject: [PATCH] Added patch file.

---
 p5-Imager/patches/patch-Makefile.PL | 35 +++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 p5-Imager/patches/patch-Makefile.PL

diff --git a/p5-Imager/patches/patch-Makefile.PL b/p5-Imager/patches/patch-Makefile.PL
new file mode 100644
index 0000000000..4485071b51
--- /dev/null
+++ b/p5-Imager/patches/patch-Makefile.PL
@@ -0,0 +1,35 @@
+$NetBSD: patch-Makefile.PL,v 1.1 2005/09/13 17:01:02 kuli0020 Exp $
+
+--- Makefile.PL.old	Sun Dec 12 05:52:00 2004
++++ Makefile.PL	Wed Feb 16 09:53:41 2005
+@@ -147,30 +147,6 @@
+   }
+ 
+  RETR:
+-  if (($formats{'gif'} or $formats{'ungif'}) && !$ENV{IM_SUPPRESS_PROMPT}) {
+-    print <<EOFF;
+-
+-You have libgif or libungif installed.  They are both known to have
+-bugs.  Imager can crash or display other strange behaviour after
+-reading or writing gif images.  Some of the gif tests can even fail
+-since they stress some parts of the buggy code.
+-
+-libungif 4.1.2 and later is safe.  giflib 4.1.3 needs at least one
+-patch to have all the bugs fixed, see README for details.
+-
+-Of course it's possible your operating system distributor has patched
+-all of these problems and you have nothing to worry about.
+-
+-Do you want to remove gif support? [Y/n]
+-EOFF
+-    my $resp = <STDIN>;
+-    chomp($resp);
+-    if ($resp ne "n") {
+-      delete $formats{'gif'};
+-      delete $formats{'ungif'};
+-      return;
+-    }
+-  }
+ 
+   for my $frm (qw(gif ungif)) {
+     checkformat($frm) if ($MANUAL and $formats{$frm});