From spencer.graves at pdf.com  Fri Apr  4 22:54:54 2008
From: spencer.graves at pdf.com (Spencer Graves)
Date: Fri, 04 Apr 2008 13:54:54 -0700
Subject: [Rd] R CMD check should check date in description
In-Reply-To: <18422.37414.77562.517176@ron.nulle.part>
References: <f8e6ff050804041205i18227c9dq41dbe5c4241b5605@mail.gmail.com>
	<18422.37414.77562.517176@ron.nulle.part>
Message-ID: <47F6959E.9050108@pdf.com>

      What do you think about adding this to section 1.1.1 of "Writing R 
Extensions", something like the following, between the paragraphs on 
"The 'package' and 'version' fields" and "The 'License' field: 


      The optional 'Date' field can be either a fixed date (preferably 
in the yyyy-mm-dd format conforming to the ISO standard) or as "Date:  
$Date$" or "Date:  $LastChangedDate$" so this field caries the package 
build date or last changed date, respectively. 


      Spencer

Dirk Eddelbuettel wrote:
> On 4 April 2008 at 14:05, hadley wickham wrote:
> | I'm always forgetting to update the date in DESCRIPTION.  Would it be
> | possible to add a warning to R CMD check if it's old?
>
> As I mentioned to Hadley in private mail, a version control system can update
> a field like $Date$ or $LastChangedDate$ automagically on writes or
> checkins. I use that as I also tend to forget to update the field manually.
> For SVN one must set one of the arcane propset fields.
>
> Hth, Dirk
>
> --
> Three out of two people have difficulties with fractions.
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>
>



[Rd] R CMD check should check date in description
Spencer Graves