src/contrib/ policy

[Matthew Dillon]

:After searching through the archives to find the policy on
:src/contrib/ I'm having a hard time wrapping my head around why
:we make a new directory for each version that gets imported.  I can
:understand the "don't commit any changes to the vendor branch and
:use the patch system for changes" policy, but why not import new
:versions in the same directory under contrib/?  For example, if I
:want to update ncurses, why not just import into src/contrib/ncurses/
:and use the appropriate release tags on the vendor branch?  It seems
:like we're adding a lot of bloat to the cvs repo the way we are
:doing it now.
:
:--Peter

    Well, we don't always adhere to that policy, but the main reason
    is so we can bring the new version in and get it working before we
    hook it all up into the build, and so we can flip back to the old
    version if we screw up.  I suppose it also keeps us honest to a 
    degree.. if we do fresh imports we know that the concept of doing
    fresh imports works.  But it is mostly a convenience.

						-Matt