On 05/15/2009 12:01 AM, Bryan Schneiders wrote:
I understand adding an optional feature to search such a path for snippets, but I think it would be entirely inappropriate to force users to adopt this strategy.
Oh of course, I agree. I'm just proposing a better way to sort the ones we ship. since we're shipping more and more lately. And when contributions for other distributions come (maybe a debian equivalent for the current network config stuff, for example), I just thought it would be nice to have it clear exactly what's meant for what. You could still use whatever you like, and this wouldn't prevent you from using any snippet in any kickstart, I wasn't talking about splitting up namespaces in cheetah or anything.
However, the pain it would cause is that our shipped snippets are suddenly somewhere else under /var/lib/cobbler/snippets, and that could break existing templates, which would have to reference the snippets at their new location, so this is the downside. If people don't think it's worth it, than that's fine by me as well. :)
-Jasper