Thank you!
Your code worked!

I tested all the combinations and this shows that, in addition to the
'rattle', in this launcher code the 'utils' package is required, otherwise
'rattle' do not launch. Without all other packages 'rattle' starts very
well. But what will be better, the inclusion or not of the 'datasets',
'grDevices', 'graphics', 'stats' and 'methods' packages in this launcher
code? I do not understand if they are needed for proper functioning of the
'rattle'.

Regards,
Iurie


2011/4/16 Prof Brian Ripley

> This is a result of bugs in rattle.
>
> The first bug is that you are explicitly asked on its help page not to use
> installed.packages() in that way.
>
> Second, packages should be able to be loaded in a session with just base
> loaded, so rattle's startup code should have utils::installed.packages().
>  (In this case it is invoked from rattle(), AFAICS, hence not invoked in the
> loading tests in R CMD check.)
>
> However, your startup code is wrong: from ?options
>
>     ‘defaultPackages’: the packages that are attached by default when
>          R starts up.  Initially set from value of the environment
>          variable ‘R_DEFAULT_PACKAGES’, or if that is unset to
>          ‘c("datasets", "utils", "grDevices", "graphics", "stats",
>          "methods")’.  (Set ‘R_DEFAULT_PACKAGES’ to ‘NULL’ or a
>          comma-separated list of package names.)
>          ^^^^^^^^^^^^^^^
>
> And by default, R_DEFAULT_PACKAGES is unset.  Try
>
> sh -c 'R_DEFAULT_PACKAGES="datasets,utils,grDevices,graphics,stats,rattle"
> R "$@"'
>
> (You may or may not need 'methods' as well.)
>
>

	[[alternative HTML version deleted]]

