On Thu, May 14, 2009 at 3:08 PM, Jasper Capel capel@stone-it.com wrote:
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.
I agree and disagree with you Jasper. In theory, the idea is fantastic. But the problems are somewhat obvious. Why not just include some sort of comment that says what "distribution-type" it is written for? If you wanted to be real crazy, make a machine readable magic comment so cobbler could (potentially) warn if you are using a debian snippet that hasn't been modified with a --breed=redhat host or whatnot?
Not that I'm a super huge fan of magic comments, but it could address a bit of both sides with less cons perhaps. An example would be the keep_ssh_keys snippet I submitted that uses "list-harddrives". With a fair amount of work list-harddrives could be removed and it could work on any generic distro. I chose to implement it for the platform we deploy however so list-harddrives is "good enough TM". Just another idea for you to chew on.