From roebuck at mdanderson.org  Mon Nov 14 22:57:04 2005
From: roebuck at mdanderson.org (Paul Roebuck)
Date: Mon, 14 Nov 2005 15:57:04 -0600 (CST)
Subject: [Rd] Package manpage DCF hooks
In-Reply-To: <971536df0511140012t5b9a2ee0vfd72dbb66c574a11@mail.gmail.com>
References: <Pine.OSF.4.58.0511140146400.518678@wotan.mdacc.tmc.edu>
	<971536df0511140012t5b9a2ee0vfd72dbb66c574a11@mail.gmail.com>
Message-ID: <Pine.OSF.4.58.0511141539060.32647@wotan.mdacc.tmc.edu>

On Mon, 14 Nov 2005, Gabor Grothendieck wrote:

> On 11/14/05, Paul Roebuck <roebuck at mdanderson.org> wrote:
>
> > Was looking at what was output for <pkgname>-package.Rd
> > and wondered if any there was any means (via macro, etc)
> > to merge some of the same information with a template
> > for my package manpage? As much (all?) of the generated
> > information was already provided in the DESCRIPTION, I'd
> > prefer not to have to update the information in multiple
> > places. I'm thinking here that I could provide a template
> > file "<pkgname>-package.Rd.in" and during build, the
> > DCF information could be substituted appropriately and
> > "<pkgname>-package.Rd" would be output.
> >
> > see also:
> >    promptPackage method
>
> What I do is make my whatever-package.Rd page be
> the central page where one can get a list of all
> the other places one can look for info (rather than
> placing the info itself there).  See, for example,
>
> library(dyn)
> package?dyn
>

Thanks for your reply. That gives me some additional
ideas but still think being able to display DCF
information and public function listing would be a nice
thing to have. For example, 'dyn-package.Rd' repeats its
DCF description.

----------------------------------------------------------
SIGSIG -- signature too long (core dumped)



[Rd] Package manpage DCF hooks
Paul Roebuck