Yes, something like that would be better - the current approach leaves a
small but exploitable race condition. I have no opinion on whether the
race condition matters in practice, of course, but my gut says that the
extra effort to use safe coding practices is so small that it's probably
Package: r-base-core
Severity: grave
Hi, maintainer!
This message about the error concerns a few packages at once. I've
tested all the packages (for Lenny) on my Debian mirror. All scripts
of packages (marked as executable) were tested.
In some packages I've discovered scripts with errors
This is the same as the one I just answered for r-base-core-ra as
r-base-core-ra is an extension/specialisation of r-base-core.
So again:
# test functionality of the compiler
javac_works='not present'
if test -n $JAVAC; then
javac_works='not functional'
rm -rf /tmp/A.java /tmp/A.class
This one time, at band camp, Dirk Eddelbuettel said:
This is the same as the one I just answered for r-base-core-ra as
r-base-core-ra is an extension/specialisation of r-base-core.
So again:
# test functionality of the compiler
javac_works='not present'
if test -n $JAVAC; then
On 25 August 2008 at 01:43, Stephen Gran wrote:
| This one time, at band camp, Dirk Eddelbuettel said:
|
| This is the same as the one I just answered for r-base-core-ra as
| r-base-core-ra is an extension/specialisation of r-base-core.
|
| So again:
|
| # test functionality of the
This one time, at band camp, Dirk Eddelbuettel said:
On 25 August 2008 at 01:43, Stephen Gran wrote:
| This one time, at band camp, Dirk Eddelbuettel said:
|
| This is the same as the one I just answered for r-base-core-ra as
| r-base-core-ra is an extension/specialisation of
6 matches
Mail list logo
