Changes since last packaged version (0.2.12): this
changes list comes from the NEWS file in the distribution tarball
and some changes are listed under section "Changes in scli 0.3.2"
even if the advertised version is 0.3.1. And more these changes
are effectively present in the 0.3.1 version!?
Changes in scli 0.3.2:
- new "show bridge vlan info" command
- new "show bridge vlan details" command
- removed the SNMP specific option which are now provided by gsnmp
- dropped getopt in favour of glib's option parsing library
- reworked the behaviour on an non-interactive tty (aka protocol mode)
- minor bug fixes plus some new bugs
Changes in scli 0.3.1:
- many new commands (I am too lazy to list them here)
- scli now uses gsnmp which uses gnet
- IPv6 support and some SNMP over TCP support
- some initial support for SNMP URLs
- minor bug fixes plus some new bugs
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.
which are the full option names used to set rpath directives for the
linker and the compiler, respectively. In places were we are invoking
the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is
inserted in case the flag is a word, e.g. -rpath. The default values
of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the
compiler that you use. They may be overridden on a ${OPSYS}-specific
basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG,
respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
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.
As seen in libc, prevent gcc's memory usage from exploding during
optimizing of SHA code by moving each round into a separate function on
sparc64.
Also remove TEXINFO_REQ, scli.{texinfo,info} are patched and touched in
such a way that makeinfo is not required for build and of course it was
not for "running": devel/gtexinfo is no more a dependency on most
NetBSD system and most of !NetBSD pkgsrc platforms.
XXX This TeXinfo/Info files issue will be more cleanly addressed soon
and wholesale...
Bump PKGREVISION.
The scli package was written to address the need for small and efficient
command line utilities to monitor and configure network devices and
host systems. The scli package is based on the SNMP management
protocol.
To summarize, the slogan for this little package is:
"After more than 10 years of SNMP, I felt it is time for really
useful command line SNMP monitoring and configuration tools. ;-)"
