[16146] in Kerberos_V5_Development
Re: Profile include support, round 2
daemon@ATHENA.MIT.EDU (Nicolas Williams)
Wed Aug 25 16:45:35 2010
Date: Wed, 25 Aug 2010 15:44:42 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: ghudson@mit.edu
Message-ID: <20100825204441.GB17097@oracle.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <201008251814.o7PIE2Bq002733@outgoing.mit.edu>
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Wed, Aug 25, 2010 at 02:14:02PM -0400, ghudson@MIT.EDU wrote:
> Although Ken didn't specifically ask for a change, I've decided that
> it would be more conservative to ensure that include profile fragments
> are syntactically independent of their parents.
>
> My first thought was to reset the syntactic parsing state before and
> after each include, but I thought of a simpler design: use a fresh
> state for included files, sharing only the root section with the
> parent. So if you do something pathological like:
I agree, the included files should be plain profiles, as opposed to
being treated as if they were cut-n-pasted into the profile where they
are included.
> I don't expect anyone to do anything that pathological. But I could
> see people doing something like:
>
> [plugins]
> includedir /etc/krb5/plugins
> # plugin fragments just assume they're already in the [plugins]
>
> and I don't really want us to have to support that.
Indeed.
> Does this design revision sound okay? I will commit the change and
> update the project proposal, but it's easily reverted if the dev
> community prefers the preprocessor-like approach I began with.
Yes.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
