Update of /cvsroot/fink/dists/10.4/unstable/main/finkinfo/languages
In directory sc8-pr-cvs5.sourceforge.net:/tmp/cvs-serv21726

Modified Files:
        iverilog.info 
Removed Files:
        iverilog.patch 
Log Message:
New upstream iverilog (0.8.4).

Tests passed: 756, Parse Errors: 0, Unsupported: 8, failed execution, 49, 
crashed: 0, C compiler err: 31 total: 860


Index: iverilog.info
===================================================================
RCS file: 
/cvsroot/fink/dists/10.4/unstable/main/finkinfo/languages/iverilog.info,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- iverilog.info       12 Jul 2006 17:10:15 -0000      1.3
+++ iverilog.info       2 Apr 2007 01:19:48 -0000       1.4
@@ -1,7 +1,7 @@
 Package: iverilog
 # Remember to fix Source line as well:
-Version: 0.8.1
-Revision: 1001
+Version: 0.8.4
+Revision: 1000
 Depends: readline5-shlibs
 Provides: verilog
 
@@ -10,10 +10,10 @@
 BuildDepends: gperf, readline5, libncurses5, bison (>= 2.0)
 
 Source: ftp://ftp.icarus.com/pub/eda/verilog/v0.8/verilog-%v.tar.gz
-Source-MD5: 61ab44cbf1734acf1b1e6c4c1ed596b6
+Source-MD5: e1ec55702622ad7522ebc6f357b9f2ce
 # SourceDirectory: verilog-%v
 
-Patch: %n.patch
+# Patch: %n.patch
 
 # Bug list:
 #
@@ -84,6 +84,8 @@
 <<
 
 DescPackaging: <<
+$LastChangedRevision: 373 $ in my local repository.
+
 SetCXXFLAGS is used because CPPFLAGS does not appear to be honored (this
 problem manifests itself as an inability to find readline/readline.h).
 <<

--- iverilog.patch DELETED ---


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fink-commits mailing list
Fink-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-commits

Reply via email to