Now the only time that libslang.so links against libtermcap.so only when
we're using termcap. In the case where we don't, libslang.so includes
its own terminfo database parser, so we don't need to link against any
curses or other terminfo library.
Bump the PKGREVISION to 7.
the library containing termcap functions) and MISC_TERMINFO_DIRS
(the location of the terminfo database). Patch the configure script
to use these values instead of using its own broken logic to determine
the same information.
+ Include termlib.buildlink3.mk to determine the right terminal library
to use.
The above two changes should fix PR pkg/30725.
+ Move the HTML documentation into ${PREFIX}/share/doc/slang.
Bump the PKGREVISION to 6.
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
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.
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".
intended transformation: use "rm" to remove an option, "rmdir" to remove
all options containing a path starting with a given directory name, and
"rename" to rename options to something else.
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
curses.buildlink2.mk. This was wrong because we _really_ do want to
express that we want _n_curses when we include the buildlink2.mk file.
We should have a better way to say that the NetBSD curses doesn't
quite work well enough. In fact, it's far better to depend on ncurses
by default, and exceptionally note when it's okay to use NetBSD curses
for specific packages. We will look into this again in the future.
Changes since 1.4.8
1. src/slarray.c: superfluous call to SLclass_add_math_op removed
(Michael Noble)
2. src/slang.c: foreach (NULL) using("next"){} foo (); caused _NARGS=1
in foo.
3. src/slarrfunc.c: Fix to prevent sum(NULL) from causing a core-dump.
4. src/slimport.c: import (module, "") made equivalent to
import(module,"Global"); This way, import(module, current_namespace())
will work when the current namespace is anonymous.
5. src/slospath.c: Several users have requested that I add the ability
to define a load path and use that path when loading interpreter
files. To this end, several new functions were added to the API:
char *SLpath_get_load_path (void);
int SLpath_set_load_path (char *path);
/* Get and Set the path to be searched for files */
int SLpath_get_path_delimiter (void);
SLpath_set_path_delimiter (int delimiter);
/* Get and set the character delimiter for search paths */
int SLang_load_file_verbose (int verbose);
/* if non-zero, display file loading messages */
New intrinsics include:
set_slang_load_path
get_slang_load_path
path_get_delimiter
These functions, nor the intrinsics have an effect on applications
that use SLang_load_file_hook or SLns_load_file_hook for loading
files. The change should be transparant to applications that use
the stock load file mechanism. The main difference is that if one
attempts to load a file with no extension, e.g., "foo", but the
file does not exist, then the interpreter will try to load the more
recent of "foo.sl" and "foo.slc".
See src/slsh.c for how the functions may be used.
6. slsh/slsh.c: Updated to use the new search path code outlined
above. Also, slsh is distributed with a collection of general
purpose slang functions, including jed's provide/require functions.
See slsh/README for more information.
7. doc/tm/cslang.tm: Modified the section describing the implemetation
of intrinsic functions in an effort to clarify the discussion.
8. src/slang.c: tiny memory leak resulting from peephole optimzations
added earlier found and fixed.
9. src/slarrmisc.c: new intrinsic: cumsum computes the cumulative sum
of an array via the new SLarray_map_array function.
