aboutsummaryrefslogtreecommitdiff
path: root/doc/ideas.rst
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2021-03-15 17:35:53 -0700
committerSean Whitton <spwhitton@spwhitton.name>2021-03-15 17:35:53 -0700
commitfe9360c286f2c4e002b3c5a98435941fb12d2c64 (patch)
treef9ee87e4138cb8e991f56b6445f4de6430615967 /doc/ideas.rst
parent5e014dfaf8775bcb9b908f9ef05f31d4b2fda56e (diff)
downloadconsfigurator-fe9360c286f2c4e002b3c5a98435941fb12d2c64.tar.gz
idea about DEFPROPLIST
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'doc/ideas.rst')
-rw-r--r--doc/ideas.rst8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/ideas.rst b/doc/ideas.rst
index c2996fa..bd55de0 100644
--- a/doc/ideas.rst
+++ b/doc/ideas.rst
@@ -65,6 +65,14 @@ Core
But maybe this is unnecessarily complex -- wouldn't it be better to just
fail and fix your deployment definitions?
+- It's not clear that the current implementation of DEFPROPLIST can support
+ everything we might want to do with it. An alternative approach to try out
+ would be for a call to DEFPROPLIST to expand into a macro definition, where
+ the new macro expands into the properties to be combined with DEFPROPLIST,
+ surrounded by ESEQPROPS. Calls to this new macro can then just be added to
+ propspecs by users. So in effect we would have a macro which can be used in
+ place of a propapp.
+
Project & packaging
-------------------