Commit 10052659 authored by Sven Neumann's avatar Sven Neumann

removed check for broken versions of perl in script-fu-xgettext

since it seems to work just fine.

removed obsolete installation instructions in plug-ins/dbbrowser


--Sven
parent c497d9c1
2000-03-29 Sven Neumann <sven@gimp.org>
* plug-ins/dbbrowser/doc/doc: removed obsolete installation
instructions
2000-03-29 Michael Natterer <mitch@gimp.org>
* app/bezier_select.h
......
put files in the right directories :
$ cd /usr/src
$ tar zvf dbbrowser-x.xx.tar.gz
$ cd dbbrowser-x.xx
$ cp *.c *.h compile_dbbrowser ../gimp-0.99.xx/plug-ins
compile & install dbbrowser :
$ cd gimp-0.99.xx/plug-ins
$ sh ./compile_dbbrowser
$ cp dbbrowser ~/.gimp/plug-ins/
patch script-fu :
$ cd gimp-0.99.xx/plug-ins/script-fu
$ patch < ../../dbbrowser-x.x/dbbrowser-script-fu-console.patch
(it modifies script-fu-console.c and Makefile.in)
compile & install script-fu with browse :
$ make
$ make install
test dbbrowser :
$ gimp
-> Xtns/DB Browser
-> Xtns/Script-Fu/Console
<thomas@maisel.int-evry.fr>
2000-03-29 Sven Neumann <neo@wintermute.ochsenblut.de>
* script-fu-xgettext: removed the check for broken versions of
perl, since it seems to work. If make or update.sh goes into an
infinite loop on your machine, please report your version of perl.
2000-03-28 Sven Neumann <sven@gimp.org>
* Makefile.in.in
......
......@@ -4,10 +4,14 @@
# adapted from pxgettext as found in the plug-ins/perl directory
# 5.005_02 in particular seems to have a BIG BUG
# There are rumors that perl version 5.005_02 has a bug
# resulting in an endless loop and a memory leak in the
# regex machinery :(
exit 1 unless $] > 5.005_02;
# regex machinery.
#
# It seems to work however. I'll leave this check commented out until
# people report problems.
#
# die ("Your version of Perl (5.005_02) is broken!\nCan't extract the strings from the scripts.\nA lot of messages will be missing from your gimp-script-fu.pot file.\n\n") if $] eq 5.005_02;
undef $/;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment