Sorry, let me provide the details:
My package has a .onAttach function (not a .onLoad).  The .onAttach
constructs a startup message and delivers it via packageStartupMessage().
 I've pasted the code below.  My package has a number of other packages
in Depends and Imports.  Some of the packages in Imports have startup
message (not R message, but package specific messages).

For example I have PerformanceAnalytics in Imports and it shows:
"Econometric tools for performance and risk analysis.
..."

googoleVis shows:
"Please read the Google Visualisation & Maps API Terms of Use
before you use the package:
..."

my .onAttach is pretty simple:
.onAttach <- function(...)
{
    mylib = dirname( system.file( package = "spear" ) )
    ver   = packageDescription( "spear" , lib = mylib )$Version
    builddate = packageDescription( "spear" , lib = mylib )$Date
    startupMessage = ""
    startupMessage = paste( startupMessage , "\n\n\n" , sep = "" )
    startupMessage = paste( startupMessage ,
"--------------------------------------------------------------------------------------------------------------------\n"
, sep = "" )
    startupMessage = paste( startupMessage , "SPEAR\n" , sep = "" )
    startupMessage = paste( startupMessage , paste( "(Version " , ver , ",
built: " , builddate , ")\n\n" , sep = "" ) , sep = "" )
    startupMessage = paste( startupMessage , "MY MESSAGE HERE...left out
for brevity" , sep = "" )
    packageStartupMessage( startupMessage )
}






On Fri, Feb 24, 2012 at 8:33 AM, Dirk Eddelbuettel <edd@debian.org> wrote:

>
> On 24 February 2012 at 00:27, Suraj Gupta wrote:
> | I don't think that is it.  My startup message is currently in .onAttach
> and I
> | still see startup message from packages that I have moved from Imports to
> | Depends.
> | Dirk?
>
> There are / were are few issues intertwined in my case, and yours may
> differ:
>
>  - are the messages from your code / packages and you startup messages ?
>
>  - are they from imported packages ?
>
>  - are they from R (reported 'foo being shadowed' or 'generic bar defined')
>
> In my case a combination of using .onAttach and .onLoad (instead of just
> .onLoad) together with import directives in a NAMESPACE file solved the
> issue, as had been suggested on this list.
>
> Dirk
>
> --
> "Outside of a dog, a book is a man's best friend. Inside of a dog, it is
> too
> dark to read." -- Groucho Marx
>

	[[alternative HTML version deleted]]

