Shibboleth Developers

[Scott Cantor <>]

> should we put the directions for compiling the source in the deploy 
> guide, or should the deploy guide just point interested parties 
> toward the cvs, and then put the directions into an INSTALL file 
> that's in the cvs?

That makes sense. I'll try to start working on that.

> my inclination is to go with option two -- we ought to document it, 
> and make  it as straightforward as we can, but I suspect  that most 
> sites will just go with the binaries, if possible.

I think that will probably change as we move from testing to production
with this code. I realize that's a ways off, but my impression is
security software usually gets built from source depending on the
paranoia/caution of the sysadmin.

> I think this would be *extremely* useful to anyone trying to build -- 
> I'm just not sure how to distribute it.

Putting it in cvs and adding it to the make dist command makes sense.

-- Scott

------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--