--- metapixel-1.0.2.orig/copying +++ metapixel-1.0.2/copying @@ -0,0 +1,341 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place - Suite 330 + Boston, MA 02111-1307, USA. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; see the file COPYING. If not, write to + the Free Software Foundation, Inc., 59 Temple Place - Suite 330, + Boston, MA 02111-1307, USA. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. --- metapixel-1.0.2.orig/debian/changelog +++ metapixel-1.0.2/debian/changelog @@ -0,0 +1,168 @@ +metapixel (1.0.2-7.2) unstable; urgency=medium + + * Non-maintainer upload. + * Build using giflib 5. Closes: #803285. + + -- Matthias Klose Wed, 16 Dec 2015 05:05:47 +0000 + +metapixel (1.0.2-7.1) unstable; urgency=low + + * Non-maintainer upload. + * Build-Depends on libjpeg-dev, not libjpeg62-dev (Closes: #643635) + + -- Didier Raboud Mon, 21 Nov 2011 10:44:46 +0100 + +metapixel (1.0.2-7) unstable; urgency=low + + * Updated standards version. + * Added misc:Depends to dependencies + + -- Chris Vanden Berghe Sat, 28 May 2011 19:31:59 +0800 + +metapixel (1.0.2-6) unstable; urgency=low + + * Changing build dependency from libungif4-dev to libgif-dev (closes: 540147) + * Made a few changes to copyright file to make package Lintian clean + * Updated to latest standards version (no changes) + + -- Chris Vanden Berghe Sun, 16 Aug 2009 20:59:54 +0800 + +metapixel (1.0.2-5) unstable; urgency=low + + * Adds metapixelrc, thanks to Wolf Wiegand for reporting this + (closes: 435294) + + -- Chris Vanden Berghe Sun, 02 Sep 2007 13:57:01 +0200 + +metapixel (1.0.2-4) unstable; urgency=medium + + * Updated build-dependencies, thanks to Regis Boudin for reporting this + (closes: 424617) + + -- Chris Vanden Berghe Sat, 12 May 2007 18:11:31 +0200 + +metapixel (1.0.2-3) unstable; urgency=low + + * Author's website changed: fixed watch file and copyright file + + -- Chris Vanden Berghe Tue, 03 Apr 2007 02:52:58 +0200 + +metapixel (1.0.2-2) unstable; urgency=low + + * fixed watch file + + -- Chris Vanden Berghe Fri, 19 Jan 2007 00:24:02 +0100 + +metapixel (1.0.2-1) unstable; urgency=low + + * Fixed typo in changelog + + -- Chris Vanden Berghe Thu, 18 Jan 2007 16:25:07 +0100 + +metapixel (1.0.2-0) unstable; urgency=low + + * New upstream release (closes:407298) + * Updated to latest standards version (no changes) + + -- Chris Vanden Berghe Thu, 18 Jan 2007 13:51:22 +0100 + +metapixel (1.0.1-1) unst able; urgency=low + + * New upstream release + * Switched to debhelper compatibility level 5 + + -- Chris Vanden Berghe Thu, 23 Feb 2006 08:43:43 +0100 + +metapixel (1.0.0-4) unstable; urgency=low + + * New maintainer email address. + + -- Chris Vanden Berghe Sat, 14 Jan 2006 00:53:48 +0100 + +metapixel (1.0.0-3) unstable; urgency=low + + * Updated to latest standards version (no changes) + * Added metapixel-imagesize, metapixel-convert and metapixel-sizesort to the + package (closes:#341099) + + -- Chris Vanden Berghe Wed, 4 Jan 2006 11:48:11 +0100 + +metapixel (1.0.0-2) unstable; urgency=low + + * Updated to latest standards version (no changes). + * Added watch file. + + -- Chris Vanden Berghe Sun, 14 Aug 2005 19:45:58 +0200 + +metapixel (1.0.0-1) unstable; urgency=low + + * New upstream version. + + -- Chris Vanden Berghe Mon, 23 May 2005 23:52:38 +0200 + +metapixel (0.11-3) unstable; urgency=low + + * Implement suggestions from Marc Brockschmidt: + - removed config target from rules file + - removed INSTALL_PROGRAM magic from rules file + + -- Chris Vanden Berghe Wed, 12 Jan 2005 20:50:27 +0100 + +metapixel (0.11-2) unstable; urgency=low + + * Patched source to solve problem with crash when one has too few images to + satisfy the minimum distance constraint + * First public upload of new upstream version (closes:#275058) + * Fixes problem with prepare script and non-image files (closes:#275948) + + -- Chris Vanden Berghe Wed, 17 Nov 2004 01:54:54 +0100 + +metapixel (0.11-1) unstable; urgency=low + + * New upstream version + + -- Chris Vanden Berghe Tue, 5 Oct 2004 07:51:13 +0200 + +metapixel (0.10-2) unstable; urgency=low + + * Fixed globbing problem + + -- Chris Vanden Berghe Sun, 3 Oct 2004 23:49:18 +0200 + +metapixel (0.10-1) unstable; urgency=low + + * New upstream version + * This version has an improved prepare script (closes:#257948). + * The manpage is provided by the developer now. + + -- Chris Vanden Berghe Tue, 28 Sep 2004 22:49:37 +0200 + +metapixel (0.9-4) unstable; urgency=low + + * Fixed short description of package (removed 'a') + * Changed debian section from utils to graphics + * Shared library dependencies are now calculated dynamically + * Standards-version bumped up to 3.6.1.0 (no changes needed) + * Added usage section to manual + + -- Chris Vanden Berghe Wed, 23 Jun 2004 9:52:16 +0200 + +metapixel (0.9-3) unstable; urgency=low + + * Fixed typo in rules file found when running build in pbuilder. + * Added docbook-xml to build-dependencies. + * Changed doctype of metapixel.xml + + -- Chris Vanden Berghe Wed, 16 Jun 2004 10:43:11 +0200 + +metapixel (0.9-2) unstable; urgency=low + + * Rules file clean-up + + -- Chris Vanden Berghe Wed, 13 Jun 2004 23:41:01 +0200 + +metapixel (0.9-1) unstable; urgency=low + + * Initial Release. (closes:#247483) + + -- Chris Vanden Berghe Wed, 5 May 2004 13:47:41 +0200 --- metapixel-1.0.2.orig/debian/compat +++ metapixel-1.0.2/debian/compat @@ -0,0 +1 @@ +5 --- metapixel-1.0.2.orig/debian/control +++ metapixel-1.0.2/debian/control @@ -0,0 +1,17 @@ +Source: metapixel +Section: graphics +Priority: optional +Maintainer: Chris Vanden Berghe +Build-Depends: debhelper (>= 5.0.0), libpng12-dev, libjpeg-dev, xsltproc, docbook-xsl, docbook-xml, libgif-dev +Standards-Version: 3.9.1 + +Package: metapixel +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends} +Description: generator for photomosaics + Metapixel is a program for generating photomosaics. It can generate + classical photomosaics, in which the source image is viewed as a matrix + of equally sized rectangles for each of which a matching image is + substitued, as well as collage-style photomosaics, in which rectangular + parts of the source image at arbitrary positions (i.e. not aligned to a + matrix) are substituted by matching images. --- metapixel-1.0.2.orig/debian/copyright +++ metapixel-1.0.2/debian/copyright @@ -0,0 +1,12 @@ +This package was debianized by Chris Vanden Berghe on +Wed, 5 May 2004 13:47:41 +0200. + +It was downloaded from http://www.complang.tuwien.ac.at/schani/metapixel/ + +Upstream Author: Mark Probst (schani@complang.tuwien.ac.at) + +Copyright 1999 Mark Probst + +You are free to distribute this software under the terms of the GNU General +Public License. On Debian systems, the complete text of the GNU General Public +License can be found in the file `/usr/share/common-licenses/GPL-2'. --- metapixel-1.0.2.orig/debian/dirs +++ metapixel-1.0.2/debian/dirs @@ -0,0 +1,2 @@ +usr/bin +usr/share/man/man1 --- metapixel-1.0.2.orig/debian/docs +++ metapixel-1.0.2/debian/docs @@ -0,0 +1,3 @@ +NEWS +README +metapixelrc --- metapixel-1.0.2.orig/debian/rules +++ metapixel-1.0.2/debian/rules @@ -0,0 +1,57 @@ +#!/usr/bin/make -f +# -*- makefile -*- +# Sample debian/rules that uses debhelper. +# GNU copyright 1997 to 1999 by Joey Hess. + +# Uncomment this to turn on verbose mode. +#export DH_VERBOSE=1 + +CFLAGS = -Wall -g +PREFIX = $(CURDIR)/debian/metapixel +BINDIR = $(PREFIX)/usr/bin +MANDIR = $(PREFIX)/usr/share/man + +build: build-stamp + +build-stamp: + dh_testdir + $(MAKE) MANPAGE_XSL=/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl + touch build-stamp + +clean: + dh_testdir + dh_testroot + rm -f build-stamp + [ ! -f Makefile ] || $(MAKE) clean + dh_clean + +install: build + dh_testdir + dh_testroot + dh_clean -k + dh_installdirs + $(MAKE) install PREFIX=$(PREFIX) BINDIR=$(BINDIR) MANDIR=$(MANDIR) + +binary-indep: build install + +binary-arch: build install + dh_testdir + dh_testroot + dh_installchangelogs + dh_installdocs + dh_installexamples + dh_installman + dh_link usr/share/man/man1/metapixel.1 usr/share/man/man1/metapixel-prepare.1 + dh_link usr/share/man/man1/metapixel.1 usr/share/man/man1/metapixel-imagesize.1 + dh_link usr/share/man/man1/metapixel.1 usr/share/man/man1/metapixel-sizesort.1 + dh_strip + dh_compress + dh_fixperms + dh_installdeb + dh_shlibdeps + dh_gencontrol + dh_md5sums + dh_builddeb + +binary: binary-indep binary-arch +.PHONY: build clean binary-indep binary-arch binary install --- metapixel-1.0.2.orig/debian/watch +++ metapixel-1.0.2/debian/watch @@ -0,0 +1,2 @@ +version=3 +http://www.complang.tuwien.ac.at/schani/metapixel/files/metapixel-(.*).tar.gz --- metapixel-1.0.2.orig/news +++ metapixel-1.0.2/news @@ -0,0 +1,98 @@ +Changes in version 1.0.1: + + * Bugfixes + + * sizesort renamed to metapixel-sizesort. + + * Improvements to metapixel-sizesort. + + * RPM SPEC file added. + +Changes in version 1.0.0: + + * Bugfixes + +Changes since version 0.11: + + * The tables files must now always be in the directory where the + small images reside, and that directory is now called a "library". + + * Metapixel can now take default values for its settings from a + configuration file in the user's home directory (".metapixelrc"). + + * Bugfixes + +Changes since version 0.10: + + * Metapixel can now enforce a minimum image distance for + collages. + + * metapixel-prepare can now traverse the image directory + recursively (courtesy of Jake Di Toro). + + * The tables file must now no longer be redirected to stdin + but it's name must be given to the option '--tables'. + This option can be used several times, so more than one + tables file can be read. + + * The default minimum distance for classical mosaics is + now 5 instead of 0. + + * A rudimentary man page is now included (courtesy of + Debian's Chris Vanden Berghe). + + * Reading the tables file is now more than twice as fast. + + * Bugfixes + +Changes since version 0.9: + + * Fixed a bug that prevented global search from working on + non-square images + + * Got rid of libzoom, so now Metapixel is standard GPL + + * Added the sizesort utility for sorting images by size + +Changes since version 0.8: + + * Global search mode + + * Protocol writing and reading + + * Antimosaic + +Changes since version 0.7: + + * Scaling of input image added + + * Tremendous memory usage improvement for classical mosaics + +Changes since version 0.6: + + * Introduces the subpixel image comparison metric + +Changes since version 0.5: + + * Cheat option + +Changes since version 0.4: + + * Bugfixes + + * Minimum distance between two instances of the same constituent + image can be specified + +Changes since version 0.3: + + * Bugfixes + + * Speed improvements + + * Got rid of ImageMagick + +Changes since version 0.2: + + * Bugfixes + + * Speed improvements --- metapixel-1.0.2.orig/readme +++ metapixel-1.0.2/readme @@ -0,0 +1,380 @@ +Metapixel 1.0.2 +=============== + +Metapixel is a program for generating photomosaics. It can generate +classical photomosaics, in which the source image is viewed as a +matrix of equally sized rectangles for each of which a matching image +is substitued, as well as collage-style photomosaics, in which +rectangular parts of the source image at arbitrary positions (i.e. not +aligned to a matrix) are substituted by matching images. + + +Installation +------------ + +To compile Metapixel, you need, in addition to a C compiler, libpng, +libjpeg, and giflib. To run the script for preparing constituent +images, you will additionally need Perl. Most Linux distributions +contain these software packages. On MacOS X, you can get them with +Fink (http://fink.sourceforge.net/). + +Edit the first line of Makefile if you want to install Metapixel +somewhere else than /usr/local. Then, type + + make + +If everything compiled fine, become root and type + + make install + + +Configuring Metapixel +--------------------- + +You can optionally create a file ".metapixelrc" in your home directory +to store some settings which makes it easier to use Metapixel, since +you won't have to use that many switches on the command line. + +A sample configuration file is included in the Metapixel distribution +under the name "metapixelrc". See the section "The Configuration +File" below for details. It is advisable to at least set the options +"prepare-directory" and "library-directory". + + +Preparing images +---------------- + +Before (non-anti-mosaic) mosaics can be created, the constituent +images need to be preprocessed. Preparing an image does two things. +Firstly, it computes various coefficients by which the image can be +matched against a part of a source image. Secondly, the image is +scaled to a smaller size. Usually this will be the size you intend to +use for it in the target image, but it can be any arbitrary size. It +makes sense to scale your images to the maximum size that you will use +for constituent images. That way, no information gets lost. The +default size is 128x128 pixels. The matching data and the scaled +images are stored in a directory which is then called a "library". +You can use more than one library in the creation of a mosaic. + +To simplify the task of creating a library, the Perl script +'metapixel-prepare' is included in the distribution. It must be +called with the name of the directory where your original images are +stored in. As a second argument you must give the directory of the +library to which the images are to be added. If you have set a +default directory for preparing images in your configuration file, +the second argument is optional. + +If the script is called with the option "--recurse", it searches the +directory with the original images recursively, i.e., it searches all +its direct and indirect subdirectories as well. It also accepts +parameters specifying the size of the scaled down images. Just call +it - it prints out usage information. + +If the script constantly complains that an error occurred when running +'metapixel', that probably means that metapixel is not in your path. +The other possibility is that all your images are in a format that +Metapixel doesn't like (it only supports JPEG, PNG, and GIF). + + +Creating photomosaics +--------------------- + +Input images for mosaics can have arbitrary sizes. Should you want +the created mosaic to be of a different size than the input image, use +the --scale option. It scales the input image uniformly in both +directions (i.e. obeying the aspect ratio). If the width or height of +the input image after scaling are not multiples of the width and +height of the constituent images, the input image is further scaled up +to the smallest size (larger than the input image) that obeys this +constraint, possibly changing the aspect ratio a bit. This does not +apply to collages, however. The sizes of their source images after +scaling are always left untouched. + +Metapixel produces output images in the PNG or JPEG formats, depending +on the extension of the output file name. In order to create a +classic photomosaic for the image input.jpg and write the output to +output.png with constituent images stored in the directory "images", +use the following command line: + + metapixel --library images --metapixel input.jpg output.png + +To create a collage use + + metapixel --library images --collage --metapixel input.jpg output.png + +Using the -y, -i and -q options you can change the weights for each of +the color channels. For example, to match only luminance, completely +disregarding chrominance, use + + metapixel --library images -i0 -q0 --metapixel input.jpg output.png + +The default weight for each of the channels is 1. + +Using the --cheat option you can specify the percentage by which the +resulting photomosaic should be overlayed by the original image. The +default is 0, i.e., the photomosaic is not overlayed at all. A +percentage of 100 yields, not surprisingly, the original image. A +percentage of 30 makes the photomosaic appear noticably better but is +yet small enough to go unnoticed without close inspection in most +circumstances. + +As of version 0.6, Metapixel implements two different matching +algorithms. The new metric, which is a trivial distance function, +seems to give better results while not being slower than the old +wavelet metric. The metric can be chosen using the --metric option. +The default is the new subpixel metric. + +You can use the --library option more than once to let Metapixel use +more than one library for a mosaic. + + +Classic Mosaics +--------------- + +Metapixel allows you to choose between two algorithms for finding +matching images, via the --search option. The old algorithm called +"local" simply selects the best matching image for each location, +possibly disregarding images selected in locations nearby (see below). + +The new algorithm called "global" repeats the following step until all +locations have been assigned to: Find the best match for any location +among all small images that have not already been used. This +guarantees that no small image is used twice. Obviously, it also +means that you must have at least as many small images as there are +locations in the image. + +Note that "global" is much slower and uses more memory than "local". + +The "--distance" option lets you specify the minimal distance between +two occurences of the same constituent image in the target image for +the "local" algorithm. Distance 0 means that it is allowed for the +same image to occur in adjacent positions in the matrix. The default +distance is 5, which means that there must be at least 5 images +"between" two occurences of the same image in the matrix. Note that +Metapixel is forced to select non-optimal matches for distances +greater 0. + + +Antimosaics +----------- + +Antimosaics are classic mosaics for which the small images are the +parts of a single image, possibly the input image itself, and can be +created using the --antimosaic option. Metapixel subdivides the +antimosaic file as if it were doing a mosaic of that file, but then +uses the resulting subimages as the small images for a classic mosaic. + +In case the antimosaic image and the input image are the same, +Metapixel will simply reconstruct the input image from the subimages, +because they will always match best in their original locations. To +tell Metapixel to do otherwise, you can use the +--forbid-reconstruction option, which allows you to specify a minimum +distance between the original location of a subimage and the location +it has in the resulting mosaic. + +Here's how you create an antimosaic with a minimum reconstruction +distance of 2: + + metapixel --library images -x input.jpg -f 2 --metapixel input.jpg output.png + + +The Configuration File +---------------------- + +The first thing Metapixel does is try to read the file ".metapixelrc" +in your home directory. From this file, it reads default values for +its settings, so that you don't have to give them on the command line +each time you use Metapixel. + +In this configuration file, you can use the following directives: + + (prepare-directory ) + + The library directory which metapixel-prepare should use by + default. metapixel-prepare does not automatically create the + directory if it doesn't exist, so make sure it does. + + (prepare-dimensions ) + + The size metapixel-prepare should use for the small images. + + (library-directory ) + + A library directory which Metapixel should use when creating + mosaics. You can use this directive more than once. + + (small-image-dimensions ) + + The dimensions of the small images Metapixel should use in + mosaics. + + (yiq-weights ) + + The weights for the channels to be used in matching images. + + (metric ) + + The metric Metapixel should use for matching images. This can + either be "subpixel" or "wavelet". + + (search-method ) + + The search method for creating classic mosaics. This can either + be "local" or "global". + + (minimum-classic-distance ) + + The minimum distance between two occurences of the same image in + classic mosaics with the local search method. + + (minimum-collage-distance ) + + The minimum distance (in pixels) between two occurences of the + same image in collage mosaics. + + (cheat-amount ) + + The cheat amount in percent. + + (forbid-reconstruction-distance ) + + The minimum distance between the position of subimage in the + original image and its position in the output image in an + antimosaic. + +Take a look at the file "metapixelrc" in the distribution. It gives +examples for each of the directives discussed here. + + +Collages +-------- + +To create a collage, you have to use the "--collage" option in +addition to "--metapixel". + +You can also specify a minimum distance between two occurences of the +same image, which is measured in pixels. The default value is 256. +Use the "--distance" option to change it. Note that the distance is +measured between the centers of the images, not their edges, i.e., a +minimum distance of 10 means that the centers of two occurences of the +same image must be at least 10 pixels apart. This will usually mean +that they are allowed to overlap, unless you use very tiny small +images. + +Note that Metapixel uses ridiculous amounts of memory for collage +mosaics. To create a collage photomosaics of size 2048x2048 your +machine should at least have 64MBytes RAM. + + +Protocols +--------- + +Metapixel can, in addition to producing a classical mosaic, write a +file specifying which small images it put in each of the locations. +This protocol file can then be used to reproduce the mosaic without +doing the matching again, for example to experiment with different +cheat amounts. The protocol also contains information on how good +each small image matches the original location, so you can find out +where the matches are good and where they aren't. You can also modify +the protocol and let metapixel generate a mosaic which it wouldn't +have matched itself, for whatever reason you might want to do this. + +Use the --out option to create a protocol and the --in option to +reproduce a mosaic from a protocol. The protocol file is a LISP list +with the following syntax: + + (mosaic (size ) (metapixels . )) + + and are the number of small images in the mosaic +across the width and height of the mosaic, respectively. is +a list containing lists with the following syntax: + + ( ) + + and are the position of the small image. The upper left small +image has coordinates (0,0), the lower right (-1,-1). + and must both be 1 in this version of Metapixel. is +the name of the small image file. + +A typical line in the protocol file looks like this: + + (30 23 1 1 "semiharmless.new/wallpaper07.jpg.png") ; 4792.000000 + +The number at the end of the line is the matching score. The lower +the score, the better the match. Note that the semicolon ';' +introduces a comment which lasts ends with the end of the line, so the +matching score is not part of the protocol syntax. + + +The matching algorithms +----------------------- + +The algorithm that does the image matching via wavelets is described +in the paper 'Fast Multiresolution Image Querying' by Charles +E. Jacobs, Adam Finkelstein and David H. Salesin. + +The new subpixel metric is very trivial. I suggest you consult the +source if you are interested in it. The matching function is +subpixel_compare(). + + +Sorting Images by Size or Aspect Ratio +-------------------------------------- + +Metapixel comes with a tool called `metapixel-sizesort' which sorts +images by size or aspect ratio by moving them to directories +containing only files with similar size or aspect ratio. + +An example: Let's say you have thousands of images in /my/images, and +you want them sorted by aspect ratio and placed in /my/sorted/images. +You can do this with this command: + + metapixel-sizesort --ratio=2 /my/images /my/sorted/images + +The option `2' to ratio tells metapixel-sizesort to put all those +images together whose aspect ratios are the same with an accuracy of +two places behind the comma. You might now have (among others) a +directory called /my/sorted/images/ratio_0.79 which contains all +images whose ratio between width and height is about 0.79. + + +Upgrading from versions 0.8/0.9/0.10 +------------------------------------ + +Starting from release 0.11, Metapixel requires that the tables file is +in the same directory as the small images described in that file. If +your configuration is different, all you need to do is to make sure +that all these files are in the same directory. You don't need to +remove the paths in the tables file, as Metapixel does that +automatically. + + +Upgrading from versions 0.6/0.7 +------------------------------- + +The tables file format has changed in Metapixel 0.8, but you don't +need to run 'metapixel-prepare' again. There's a program called +'convert' included in the distribution that does the job. Just tell +it which size your small images are, give it the old tables file on +stdin and it writes the new one on stdout. + +For example, if your small images are 128 pixels wide and 96 pixels +high, go to the directory with the tables file (usually the directory +where the small images are) and do + + convert --width=128 --height=96 tables.mxt + + +Licence and Availability +------------------------ + +Metapixel is free software distributed under the terms of the GPL. +The file `COPYING' contains the text of the license. + +The source of Metapixel is available at the Metapixel homepage at + + http://www.complang.tuwien.ac.at/schani/metapixel/ + +--- +Mark Probst +schani@complang.tuwien.ac.at --- metapixel-1.0.2.orig/rwimg/rwgif.c +++ metapixel-1.0.2/rwimg/rwgif.c @@ -54,7 +54,7 @@ assert(data != 0); - data->file = DGifOpenFileName(filename); + data->file = DGifOpenFileName(filename, NULL); assert(data->file !=0); @@ -137,7 +137,7 @@ } free(buffer); - assert(DGifCloseFile(data->file) == GIF_OK); + assert(DGifCloseFile(data->file, NULL) == GIF_OK); return data; }