Re: bsdcpio and bsdtar installed by default

[Thor Lancelot Simon <tls%rek.tjls.com@localhost>]

On Thu, Jun 05, 2008 at 01:55:02PM +0200, Joerg Sonnenberger wrote:
> 
> bsdtar itself is mature code, it has been the system tar on FreeBSD for
> a long time now.  It has some different defaults (e.g. --unlink is not
> the default, neither is -S).  It does not support historic legacy like
> -B.  For those two reasons I explicitly don't want to make it the
> default right now.  Most of the recent work was to add some of the
> NetBSD specific features like -S and -s.  bsdcpio on the other hard is
> much newer code and still needs validation whether some of the more
> obscure options are really desired or not.

Why don't we change the defaults to match our existing ones and make
this our default tar now?

Multiple versions of program _X_ in the tree just means that bugs linger
and code doesn't get tested as it should.

However, we are (notionally) in a "quiet period" and I am already
somewhat annoyed, as someone who maintains an external NetBSD-based
source tree and thought I knew what to expect with the release timeline,
by the amount of thrash that's occurred in the tree since the
"quiet" period started.

Bugfixes, even major ones, are one thing, but imports of large new stuff
like this really seem to me like they should have been done before the
25th or wait a while.  A little slop at a freeze date is one thing but
come on -- it's two weeks later now.

If there is enough sentiment that this kind of work should be going on
now I think maybe we should reschedule the "quiet period" to start later,
and at that time keep it "quiet" for real, not like it seems to be these
past two weeks.

Thor