| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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.
|
|
|
|
|
|
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in
http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
|
|
changes:
-java support
-MacOS X support
|
|
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
|
|
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
|
|
|
|
changes:
-allow executing expressions from the command line
-secure mode
-More intelligent parsing
-optimizations, fixes, documentation improvements
|
|
former) for applications that are known to require C++.
|
|
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.
|
|
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
|
|
|
|
Fixes recent packaging problems noted in the bulk builds.
|
|
Many, many, many additions, bug fixes, and improvements since the last
packaged version. Too many to even summarize here. Please refer to the
change log in the distfile or on the homepage.
|
|
|
|
|
|
|
|
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
|
|
|
|
|
|
|
|
rmdir -> ${RMDIR}
rm -> ${RM} (${RM} added to PLIST_SUBST)
chmod -> ${CHMOD}
chown -> ${CHOWN}
|
|
* small improvement to Arg(...) working on real numbers.
* improved 'make test', no need to install before test any more.
* VarList can now accept a second argument, a filter predicate.
* Pattern matcher now allows extended prototypes, like
PP(list_Contains("a")) <-- ... etcetera.
* c-style tokenizer using CTokenizer() (DefaultTokenizer() switches back
to the default tokenizer).
* Great speed-up of function Assoc.
* Christian Obrecht implemented the Rabin-Miller primality testing
algorithm, which greatly improves the speed of IsPrime.
* Orthogonal polynomials OrthoP, OrthoP,OrthoG,OrthoH,OrthoL,
OrthoT,OrthoU implemented by Serge Winitzki.
* various speedups, and a new memory manager, optimized for allocating
many small blocks (which is the case in Yacas).
* Changed the directory structure for the script files
* Greatly improved Simplify function.
* Added CurrentFile, CurrentLine functions
* Implemented backquote mechanism: `(...) will substitute every @a with
the evaluation of a (and if a is a function the function name is
replaced). The end result is evaluated. see substitute.cpp for more
details
many more... see http://www.xs4all.nl/~apinkus/changes.html for the complete
list.
|
|
|
|
|
|
|
|
+ move the patch digest/checksum values from files/patch-sum to distinfo
|
|
|
|
|
|
changelog 1.0.41-1.0.43:
Added the YacasNotebook directory with the emacs shell to the repository.
We have support for BeOS! Thanks to Eugenia Loli.
Serious bugfix: the ^ operator wasn't working like it should. It was mapped to BitXor, and its precedence
was wrong.
Allowed CForm to accept if (predicate) body; and if (predicate) body else other; These routines need to be
written still, however, for them to also work in Yacas itself.
cleaned up some code.
Speedup of 40% of general Yacas execution.
Some improvements to the logic theorem prover so it can handle (a>b)-type epressions.
added support for annotating expressions, with GetExtraInfo and SetExtraInfo.
Initial checkin into sourceforge CVS. Thanks to Vladimir Livshits!
Fixed some windows compilation problems. ElfDll being explicitly mentioned in mathcommands3.cc, and
explicitly including elfdll.h.
added initial versions for the c-like &, | % and ^ operators, and if (...) ... else ... . This will probably make it
possible in the future to write code that is a lot more readable than If(..., ..., ...). The else clause binds to the
last if, just like in c. So this means you can now enter expressions like: if(3 < 3) a else if (3 > 3) b else c;
|
|
there are about 8 pages of changes since the last packaged version (1.0.29).
A complete list may be found at http://www.xs4all.nl/~apinkus/infoindex.html
the changes include a large number of bug fixes, several new features such as
- Implemented ContFrac, which makes a continued fraction expansion of a number.
- Implemented Decimal. Decimal calculates an infinite decimal representation
of a number.
- Implemented LagrangeInterpolant, a way to create a polynomial that goes
through certain points.
- Implemented Select, which can select certain elements from a list based on
a predicate test function.
- Half-integer factorials (sent in by Serge Winitzki)
- Added GetPrimeFactors.
- Implemented RandomIntegerVector, RandomPoly.
plus several others.
|
|
|
|
* added a directory colorcode with code to htmlize the scripts. it also color-highlights
the code. Try it out by typing './colorcode' in that directory, and then
'netscape scriptsmain.html'
* Pattern matching code optimized a little.
* SylvesterMatrix, code supplied by James Gilbertson.
* MatrixRow, MatrixColumn, and GenMatrix supplied by James Gilbertson.
* changed Intersection and Difference, so they handle lists with multiple identical
elements correctly.
* Fixed the D(x)x+y bug reported by Fred Bacon.
* Fixed the Gcd(x,x) bug reported by Scott.
* added Factorize({list}). Factorize(1 .. 4) should now return the same as 4! for instance.
* Added Content and PrimitivePart to the univariate polynomial code. See the manual for an
explanation of these functions.
|
|
Yacas (Yet Another Computer Algebra System) is a small and highly flexible
computer algebra language. The syntax uses a infix-operator grammar
parser. The distribution contains a small library of mathematical functions,
but its real strength is in the language in which you can easily write your
own symbolic manipulation algorithms. It supports arbitrary precision
arithmetic.
The current version is 1.0.28 (the first release was 1.0.0). The language is
very much in a finished state. Any code written for it should be usable in
future versions. Also, the language should prove very easy to learn.
Yacas is written in very clean c++ code, and is very portable . It can compile
stand-alone, and is easily embeddable. Yacas contains a native arbitrary
precision arithmetic module, but can also be used with GMP.
Things implemented include: arbitrary precision, rational numeric, vector,
complex, and matrix computations (including inverses and determinants and
solving matrix equations), derivatives, solving, Taylor series, numerical
solving (Newtons method), and a lot more non-mathematical algorithms. The
language natively supports variables and user-defined functions. There is
basic support for polynomials.
|
