Garrett D'Amore writes: > Because GNU tar delivers into SFW, and does not claim to be called > "/usr/bin/tar". > > If you are happy being delivered into /usr/sfw/bin/star then much of the > work can probably be elided.
I think that's a bit of a misunderstanding. The consolidation through which a project delivers has _nothing_ to do with the path of the installed utility. In particular, there's no reason that anything new should ever be added into the /usr/sfw/bin ghetto. Delivering via SFW versus ON allows one to take advantage of the differing integration requirements of the two consolidations. For example, SFW emphasizes minimal (preferably zero) change from the external reference source, while ON emphasizes a consistent and well-known style for all components. In any event, as I mentioned before, none of this discussion has anything to do with the changing of the path for GNU tar. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
