[csw-maintainers] build requirements

[Ben Walton]

Excerpts from Trygve Laugstøl's message of Tue Dec 16 19:51:58 -0500 2008:
> 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.

As far as I've seen at this point, it's simply the test scripts that
are breaking without gnu sed.  As this shouldn't impact the runtime
requirements, I don't think there much worry of a permanent dependence
on gnulinks.

Option #2 seems like the more technically 'correct' thing to do until
you consider that the primary development environment for git is a
completely gnu userland.  At some point, a gnu-ism would creep in
again requiring more work on our part.  Going with gnulinks seems like
it's easier all around.  If it ends up impacting dependencies, then
I'll reconsider.

I appreciate the feedback though! :)

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20081216/7b15c275/attachment-0001.asc>