Path to this page:
Subject: CVS commit: pkgsrc/graphics/gifsicle
From: Lubomir Sedlacik
Date: 2003-06-01 14:14:11
Message id: 20030601121411.DE509B004@cvs.netbsd.org
Log Message:
Updated to version 1.37.
Changes:
- DESCR has 80 culumns
- whitespace
1.37:
=====
- Fix bug where combining `--rotate-X' and `-O' options would cause a
segmentation fault. Reported by Dan Lasley <Dan_Lasley@hilton.com>.
- Rearrange source tree.
1.36:
=====
* Fix subscript-out-of-range error in main.c reported by Andrea Suatoni.
1.35:
=====
- Fixed bug where `--crop' could cause a segmentation fault, present since
1.32 or 1.33. Reported by Tom Schumm <phong@phong.org>.
1.34:
=====
- Fixed bug where combining `--crop' and `-O' options could corrupt output.
Reported by Tom Schumm <phong@phong.org>.
1.33:
=====
- Be more careful about time while animating. In particular, prepare frames
before they are needed, so that they can be displayed exactly when
required. Problem reported by Walter Harms <WHarms@bfs.de>.
- More warning fixes.
1.32:
=====
- Add `--multifile' option handling concatenated GIF files. This is useful
for scripts. For example, `gifsicle --multifile -' will merge all GIF
files written to its standard input into a single animation.
- More fixes for spurious background warnings.
1.31:
=====
- Changed behavior of `--crop X,Y+WIDTHxHEIGHT' option when WIDTH or HEIGHT
is negative. Previously, zero or negative WIDTH and HEIGHT referred to
the image's entire width or height. Thus, the option `--crop 10,0+0x0'
would always lead to an error, because the crop left position (10) plus
the crop width (the image width) was 10 pixels beyond the image edge. The
new behavior measures zero or negative WIDTH and HEIGHT relative to the
image's bottom-right corner.
- Changed background behavior. Hopefully the only user-visible effect will
be fewer spurious warnings.
- Fixed a bug that could corrupt output when optimizing images with `-O2'
that had more than 256 colors.
1.30:
=====
- Fixed bug in ungif code: Writing a large ungif could corrupt memory,
leading eventually to bad output. This bug has been present since
Gifsicle could write ungifs! Bad files and assistance provided by Jeff
Brown <jabrown@ipn.caida.org>.
Files: