Robert Gentleman wrote:
> Kurt Hornik wrote:
>
>>> hadley wickham writes:
>>>
I recently thought about this. I see several issues.
* How can we determine if it is "old"? Relative to the time when the
package was uploaded to a repository?
* S
On 4 April 2008 at 23:15, Antonio, Fabio Di Narzo wrote:
| 2008/4/4, Dirk Eddelbuettel <[EMAIL PROTECTED]>:
| >
| > 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
> > To clarify, do you mean you have decided not to provide a date field
> > in the DESCRIPTION file? If so, would you mind elaborating why?
> >
>
> Sure: The date of what?
That's a good question. Another possible solution would be to remove
(or down-weight the importance of) the date field, a
2008/4/4, Dirk Eddelbuettel <[EMAIL PROTECTED]>:
>
> 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 contr
hadley wickham wrote:
>> Please no. If people want one then they should add it manually. It is
>> optional, and some of us have explicitly opted out and would like to
>> continue to do so.
>
> To clarify, do you mean you have decided not to provide a date field
> in the DESCRIPTION file? If
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 -mm-dd
Actually, now that I think about it, 'R CMD build' already adds the 'Packaged:'
field, so perhaps it wouldn't really make sense to add yet another field with
exactly the same information
-roger
Robert Gentleman wrote:
>
> Kurt Hornik wrote:
>>> hadley wickham writes:
I recently th
> Please no. If people want one then they should add it manually. It is
> optional, and some of us have explicitly opted out and would like to
> continue to do so.
To clarify, do you mean you have decided not to provide a date field
in the DESCRIPTION file? If so, would you mind elaborating wh
Kurt Hornik wrote:
>> hadley wickham writes:
>
>>> I recently thought about this. I see several issues.
>>>
>>> * How can we determine if it is "old"? Relative to the time when the
>>> package was uploaded to a repository?
>>>
>>> * Some developers might actually want a different date for
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$ au
I agree.
It sounds odd to explicitely ask someone to set the 'Date:' field and
then worring because it doesn't match your precise expectation that it
should equal the build time.
A.F.
2008/4/4, Roger D. Peng <[EMAIL PROTECTED]>:
> I don't think having 'R CMD check' spit out a warning about the d
I don't think having 'R CMD check' spit out a warning about the date would be
all that productive. I do think it would be nice to have 'R CMD build' add a
Date: field to the DESCRIPTION file if there isn't already a Date: field. And
I
think such an addition would solve the first problem since
> hadley wickham writes:
>> I recently thought about this. I see several issues.
>>
>> * How can we determine if it is "old"? Relative to the time when the
>> package was uploaded to a repository?
>>
>> * Some developers might actually want a different date for a variety of
>> reasons ...
I think its somewhat inspiring to be able to get R CMD check to the
point that there are no warnings so having a situation where a warning
is ok would interfere with that.
On Fri, Apr 4, 2008 at 3:54 PM, hadley wickham <[EMAIL PROTECTED]> wrote:
> > I recently thought about this. I see several i
> I recently thought about this. I see several issues.
>
> * How can we determine if it is "old"? Relative to the time when the
> package was uploaded to a repository?
>
> * Some developers might actually want a different date for a variety of
> reasons ...
>
> * What we currently say in
On Fri, Apr 4, 2008 at 2:26 PM, Kurt Hornik <[EMAIL PROTECTED]> wrote:
> > hadley wickham writes:
>
> > 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?
>
> I recently thought about this. I see several issues.
>
> hadley wickham writes:
> 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?
I recently thought about this. I see several issues.
* How can we determine if it is "old"? Relative to the time when the
package was u
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?
Hadley
--
http://had.co.nz/
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
18 matches
Mail list logo
