on some platforms that lacked shared library support in the past. The
list hasn't been maintained at all and the gain is very limited, so just
get rid of it.
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
2.4.3 --> 2.4.4:
----------------
Bug fixes:
NetCDF error messages should now be correct. No more "unknown errors"!
2.4 --> 2.4.1:
--------------
Bug fixes:
- Scientific.MPI did not contain the _C_API object needed by C extension
modules that call MPI.
- The arguments to the receiveString method are now optional, as documented.
2.3.3 --> 2.4:
--------------
Bug fixes:
- Memory function calculation in Scientific.Signals.Models
returned a wrong value for the first point.
- Some indexing problems in Scientific.IO.NetCDF were fixed;
none of them caused wrong results, just unjustified exceptions.
2.3.2 --> 2.3.3:
----------------
Bug fixes:
- The method divide() assumed the wrong coefficient order.
New features:
- Module Scientific.Signals.Models
- Class Scientific.Statistics.Histogram.WeightedHistogram
2.3.1 --> 2.3.2:
----------------
Incompatible changes:
- Specification of routines in Scientific.BSP changed.
2.2 --> 2.3.1
-------------
New features:
- New modules Scientific.BSP and Scientific.BSP.IO
Inspired by FreeBSD "ports".
Fix the PLISTs accordingly.
Also, while at it, remove now obsolete compileall.py calls in post-install
targets and insure that extension.mk is in included before builinlinks of
other Python modules.
Discussed with/ok'ed by drochner@.
extension Makefile fragments, because they really don't have anything to
do with the buildlink[12] frameworks. Change all the Makefiles that use
application.buildlink.mk and extension.buildlink.mk to use application.mk
and extension.mk instead.
2.1.5 --> 2.2
-------------
Bug fixes:
- The sign convention for rotation angles was not correctly applied
in Scientific.Geometry.Transformation and Scientific.Geometry.Quaternions.
Everything was consistent, but with the wrong sign.
Improvements:
- Scientific.IO.PDB can handle a larger range of variant formats for DNA
New features:
- New module Scientific.Visualization.VPython.
- Scientific.IO.TextFile also handles bzip2 compressed files
(extension .bz2). This only works if bzip2 is installed.
2.1.4 --> 2.1.5
---------------
New features:
- Scientific.TkWidgets.TkPlotCanvas:
- Popup menu on right button
- Value display on middle button
- HorizontalLine, VerticalLine objects
Modifications:
- MPI interface no longer assumes that MPI_Op and MPI_Datatype are
integers (they aren't in LAM, for example).
2.1.3 --> 2.1.4
---------------
New features:
- New MPI functions implemented by Jakob Schiotz:
- nonblocking send and receive
- abort
- reduce and allreduce
Modifications:
- The Python interpreter lock is released during calls to the netCDF
library, permitting other threads to continue during I/O operations.
An internal lock has been added to prevent reentrant calls to the
netCDF library, which is not thread safe.
(If you don't understand any of this, you shouldn't care, it has
no consequences unless you use threads.)
- Methods receive and receiveString on MPI communicator objects
can be called without source and tag arguments (defaults to None).
Bug fixes:
- The compilation script did not work correctly for MPI support
2.1.2 --> 2.1.3
---------------
New features:
- Some small utility widgets have been added to Scientific.TkWidgets.
They are not particularly "scientific", but not worth the effort
of a separate distribution.
Bug fixes:
- The abs() function didn't work on DerivVar objects (modules
Scientific.Functions.Derivatives and Scientific.Functions.FirstDerivatives)
with negative values.
- The method projectionOf in Scientific.Geometry.Objects3D.Plane was
wrong.
2.1.1 --> 2.1.2
---------------
Installation:
- The mpipython executable is compiled using 'mpicc', which should simplify
installation significantly because all library specifications are
automatically taken into account. In other words, MPI support should
work on all platforms without any modifications to the Setup file.
(Thanks to Jakob Schiotz for this suggestion!)
- Some 'extern' declarations were changed to 'staticforward' to please
some compilers.
Documentation:
- the documentation for the methods receive and receiveString were
wrong.
2.1.0 --> 2.1.1
---------------
Bug fixes:
- The upper bound for MPI message tags was not treated correctly,
leading to a bound of zero on some platforms.
Modifications:
- The methods sendArray and sendString were combined into a single
method send.
- broadcastArray was renamed to broadcast, shareArray was renamed to share,
receiveArray was renamed to receive. The only function that retains
a data type indication is receiveString.
2.0.1 --> 2.1.0
---------------
Additions:
- MPI interface in Scientific.MPI
