Skip to Content.
Sympa Menu

shibboleth-dev - Re: More defined custom extensions mechanism

Subject: Shibboleth Developers

List archive

Re: More defined custom extensions mechanism


Chronological Thread 
  • From: Chad La Joie <>
  • To:
  • Subject: Re: More defined custom extensions mechanism
  • Date: Mon, 11 Jul 2005 08:57:06 -0400
  • Organization: UIS - Project Sentinel

Tom Scavo wrote:
>>- A new extension build property, ext.install.etc. If set to 'true' it
>>will copy everything in the 'etc' directory to IDP_HOME/etc or
>>SP_HOME/etc, overwriting what is currently there. Default setting is
>>'false'.
>
>
> Something like is needed, yes, but can I make a suggestion? Change
> the property name to overwrite.ext.etc (follows existing naming
> conventions) with the following behavior:

I can rename it to ext.copy.conf which is close to what the IdP uses
(copy-idp-conf) but still matches the rest of the extension naming
conventions (purposely different than the main build to cut down on name
conflicts/mistakes).

Read below though and see if you think the current name
(ext.install.etc) makes sense.

> If true, copy ${ext.name}/etc to ${idp.home}/etc and overwrite
> anything that's there. If false (default), copy ${ext.name}/etc to
> ${idp.home}/etc but do not overwrite any existing files. This
> precludes the need to modify the property after the initial install.

No, I do not want to copy stuff but not overwrite. I think this could
lead to bad things. For example, in version 1.0 of an extension you
have foo.xml. Then in version 1.1 you have foo.xml with new, and
required stuff, as well as bar.xml. If you just copy bar.xml over you
might get all sorts of odd errors because you foo.xml wouldn't have the
new stuff in it.

Maybe some one can convince me this isn't an issue.
--
Chad La Joie 315Q St. Mary's Hall
Project Sentinel 202.687.0124



Archive powered by MHonArc 2.6.16.

Top of Page