[Scons-dev] tools and testing

[Russel Winder]

SCons policy is no tests, no entry into the repository. In the main,
this is a good thing. However, for the dub tool, it can only be tested
by making access to the Dub repository. This is a very different
scenario to the classic SCons tool which is testable entirely within a
local sandbox without access to the Internet.

Tools such as https://bitbucket.org/scons/scons/wiki/DownloadUnpack
exist only on the wiki (perhaps another examnple to make a repository
from?) and so there is no testing obligation.

So does this mean dub has no chance of entry into the main repository?
Obviously I can cope with the answer yes, but now is the time for
discussion so as to inform future management of it and the evolution of
the dmd, ldc, and gdc tools.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder at ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel at winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20170417/bd47e4fb/attachment.pgp>