From edd at debian.org  Tue Sep  4 23:42:35 2012
From: edd at debian.org (Dirk Eddelbuettel)
Date: Tue, 4 Sep 2012 16:42:35 -0500
Subject: [Rd] if(--as-cran)?
In-Reply-To: <504671FC.9030800@gmail.com>
References: <50465D7F.5060004@gmail.com>
	<0CAEE2B1235DF643B0F5E1EAE1487B530946D655@023-CH1MPN1-043.023d.mgd.msft.net>
	<20550.28445.956167.112449@max.nulle.part>
	<504671FC.9030800@gmail.com>
Message-ID: <20550.30155.399375.438614@max.nulle.part>


On 4 September 2012 at 17:26, Duncan Murdoch wrote:
| On 04/09/2012 5:14 PM, Dirk Eddelbuettel wrote:
| > An add-on argument to the already established option --as-cran may be the
| > best.
| >
| > And to iterate, what bugs me is that for _me_ on _my_ machine developing _my_
| > package I have remember how to enable what is now (as per CRAN's decree)
| > "non-standard behaviour" of full testing.  I fully agree with what Terry had
| > said: more tests are better (when we develop).  I want the full suite at my
| > end; that is after all why we wrote it!
| 
| You don't have to remember that, you need to figure it out once, write a 
| script that sets the environment variables that enable it, and then you 
| can forget it.

"In theory, theory and practice are the same. In practice, they are not."

The main test script long had exactly such a setting; I wrote what I wrote
because it is _still the wrong way around_ and as I happen to have added to
unit tests this weekend _having suffered through precisely this setting_.

But we are on different wavelengths here and I evidently do not get my point
across to you.  And as you are the one who could make a change where it
matters, I have no choice but to rest my case in frustration.

Dirk

-- 
Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com



[Rd] if(--as-cran)?
Dirk Eddelbuettel