How do I deal with puppet modules with classes of the same name? -


i have puppet module uses gini-archive. change module depend on biemond-wildfly, depends on nanliu-archive.

however, can't install nanliu-archive, because both of these archive modules install directory called archive. this, believe, violates puppet module requirements, should both install directories called <username>-archive.

however, if put them in different directories, still have problem. both classes called archive (actually 1 class , 1 define, don't think that's important right now), when module says include archive, puppet isn't going know 1 want.

note have java background every class in package hierarchy prevents these kind of issues, can't see equivalent puppet.

i know have whole load of different modules directories (/etc/puppet/modules, /etc/puppet/modules2 etc), puppet still seems through these in order, meaning load archive class first module directory in list.

is there way of solving or have reached limit of puppet can do? i'd rather not have fork every single module , change class names, seems defeat point of forge.

thanks.

the name of directory module in must archive, username used purpose of distributing , packaging modules not used puppet while autoloading. basically, seeing correct.

there seems 2 ways of handling this:

  1. fork 1 of 2 archive modules , rename module not collide
  2. fork 1 of modules using archive modules , migrate use same archive module other one. since 2 archive modules same thing, prefer method.

Comments

Popular posts from this blog

c++ - Difference between pre and post decrement in recursive function argument -

php - Nothing but 'run(); ' when browsing to my local project, how do I fix this? -

php - How can I echo out this array? -