Note:
Beginning with SQLite version 3.7.4 the naming and versioning scheme changed
again!
This update also replaces the "pure" amalgamation source tarball in favour of
the "autoconf" version, which is a tarball containing the amalgamation for
SQLite 3.7.6.2 together with an configure script and makefile for building it.
This tarball also contains in the "tea" subdirectory a separate configure
script and makefile compatible with the Tcl Extension Architecture (TEA) for
building the TCL bindings to SQLite.
Note:
According to http://search.cpan.org/dist/perl/INSTALL#Installation_Directories
this is the right place for distributions which build binary packages of perl
add-on modules.
If you wonder about the changed build process here is are the relavant
parts out of the 'subversion/bindings/swig/INSTALL' file.
-------------------------------------------------------------------------
* Perl
Perl 5.8.0 is required. You can specify the perl binary by passing
PERL=/path/to/perl as part of the configure command in the top level
of the Subversion source tree. Make sure that the Perl version used
is the same one that you configured SWIG to run against during the
SWIG configure (see above).
1. Run `make swig-pl' from the top of the Subversion source tree.
2. Run `make check-swig-pl' from the top of the Subversion source
tree, to test the bindings
3. to install run `make install-swig-pl' from the top of the
Subversion source tree.
If you need to pass extra parameters to Perl build process (Makefile.PL),
then you need to do this process somewhat different:
1. Run `make swig-pl-lib' from the top of the Subversion source tree.
2. Run `make install-swig-pl-lib'
3. cd subversion/bindings/swig/perl/native
4. Run `perl Makefile.PL EXTRAOPTIONSHERE`
5. Run `make install'
To install the Perl bindings in a location other than the system
Perl directory, use the above instructions with the extra option
PREFIX=/your/prefix/here.
-------------------------------------------------------------------------
Note:
This is nearly a complete rework of the mysql package because recent mysql
releases are using cmake for building.
In contrast to our former mysql package we use the default prefix instead
of 'opt/mysql' now, to be more FHS friendly.
Christian Wiese