From ggrothendieck at gmail.com  Mon Nov 14 09:12:31 2005
From: ggrothendieck at gmail.com (Gabor Grothendieck)
Date: Mon, 14 Nov 2005 03:12:31 -0500
Subject: [Rd] Package manpage DCF hooks
In-Reply-To: <Pine.OSF.4.58.0511140146400.518678@wotan.mdacc.tmc.edu>
References: <Pine.OSF.4.58.0511140146400.518678@wotan.mdacc.tmc.edu>
Message-ID: <971536df0511140012t5b9a2ee0vfd72dbb66c574a11@mail.gmail.com>

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


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
>
> ----------------------------------------------------------
> SIGSIG -- signature too long (core dumped)
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>



[Rd] Package manpage DCF hooks
Gabor Grothendieck