[csw-maintainers] build requirements

[Trygve Laugstøl]

Ben Walton wrote:
> Hi All,
> 
> I now have a gar description for git that builds it but am seeing
> tests fail.  So far, all failures are related to an implicit
> assumption that sed == gnu sed.  Modifying the test files to call gsed
> seems to get things going.  So, I have a few options:
> 
> 1. Create a patch per 'bad' assumption (where bad == 'bad for me
>    because it makes more work')
> 2. Add some autoconf magic, and alter the test harness to include the
>    file generated by configure, thus allowing for a user specifiable
>    $(sed) program.  Submit this upstream.
> 3. Use PREREQUISITE_PKGS += CSWgnulinks and prepend /opt/csw/gnu to
>    the GARPATH.
> 
> I have my own opinion on which is the best going forward, but am
> curious as to what others think?

Do me it sounds like do 1) first to get the package out and then work on 
2) if git is a long-term useful package that we would like to release 
often to lower our maintenance cost.

I assume that 3) would lead to requiring me having /opt/csw/gnu first in 
my path when using git and that is not going to happen.

--
Trygve