NEWS


startupmsg 1.0.0 (2025-01-12)

under the hood

We instantiated a more refined mechanism for startup messages, to avoid

unnecessary pkg version updates just triggered by startup messages issuing

version information of attached packages upstream, which changes the

reference output of the attaching package and hence creates diffs when

tested on CRAN

Somewhat more detailed, in the prior regime, suppose we had pkgs pkgA and pkgB on

CRAN, pkgB importing the NAMESPACE of pkgA via depends, and both pkgs pkgA and pkgB

had startup messages including version information, and pkgB used the reference

output pkgB-Ex.Rout.save as a unit test for pkgB. Then, whenever we submitted an

updated version of pkgA to CRAN, we had to also submit a new version of pkgB to CRAN

regardless whether we had changed anything in pkgB, because of the changed version

information in the startup message of pkgA which showed up in the reference output

when pkgA was attached at loading pkgB

To avoid this, by default our startup messages no longer issue version information

of the attached packages, but --only once per session-- we show a startup message

indicating how to show the prior behaviour, i.e., show the version information

of attached packages in the startup messages

startupmsg 0.9.7 (2024-08-29)

under the hood

with the help of K. Hornik identified spurious, platform dependent LF/CR issue

and capsulated calls to infoShow() in Rd files by

startupmsg 0.9.6 (2019-03-11)

user-visible CHANGES

startupmsg 0.9 (2013-09-13)

user-visible CHANGES

GENERAL ENHANCEMENTS

under the hood

added .Rbuildignore

BUGFIXES

startupmsg 0.8 (2013-02-07)

under the hood:

startupmsg 0.7 (2009-11-03)

user-visible CHANGES

GENERAL ENHANCEMENTS

startupmsg 0.6 (2009-04-15)

startupmsg 0.5.3 (2008-11-29)

startupmsg 0.5 (2007-07-27)

startupmsg 0.4 (2006-11-23)

startupmsg 0.3 (2006-05-12)

startupmsg 0.2

startupmsg 0.1