>This is if course incorrect: When _you_ chose to add -/ to Sun's current
>tar/cpio/pax implementation, you plan to boycott a possible future integration
>of an star based implemention to replace the old Sun programs. This is because
>_you_ chose to deliberately add an incompatible interface.
Please do not use words like "boycott" as they convey something which
clearly does not match the intention of the people integrating the
software.
Secondly, I don't think your statement is factual correct.
Stepping over the fact that there is not even an ARC case proposing
the replacement of the above mentioned commands with star, it is
clearly possible to both have this option *and* later replace the
commands with an star based implementation as long as there is
no requirement that the star source code does not change.
Even before this case, the requirement for such a replacement are
fairly simple:
- star will need to be able to read AND WRITE[1] all Solaris
compatible formats.
- star, when called as the replacement programs pax/cpio/tar
will need to behave *exactly* like the current Sun implementations
(they may have additional options but the existing options must
be preserved and work compatibly)
Both of these requirements will require work for star.
I think PSARC is well aware that the second point is affected by
PSARC 2007/459. Yet, having weighted the arguments pro and con they
do not see this as being an undue burden, a hurdle which cannot
be overcome. It is, afterall, just a simple matter of programming.
Casper
[1] In order to move, e.g., TX tar files to older Solaris releases which
do not have an star based implementation
