You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Librarian-puppet only has a development dependency on puppet, but the code for processing Git sources in a Puppetfile still uses Puppet code directly to read the Puppet metadata file to figure out the module version and it's dependencies.
If the puppet gem isn't a dependency, then we need to get rid of the Puppet metadata reader in the Git code.
Should we duplicate the metadata reading code in here (Apache2 to MIT License?), or ask Puppetlabs to break it of in a separate gem? @joshcooper, can you give the Puppetlabs perspective on this?
The text was updated successfully, but these errors were encountered:
Librarian-puppet only has a development dependency on puppet, but the code for processing Git sources in a Puppetfile still uses Puppet code directly to read the Puppet metadata file to figure out the module version and it's dependencies.
If the puppet gem isn't a dependency, then we need to get rid of the Puppet metadata reader in the Git code.
This change request is directly related to #134.
Should we duplicate the metadata reading code in here (Apache2 to MIT License?), or ask Puppetlabs to break it of in a separate gem? @joshcooper, can you give the Puppetlabs perspective on this?
The text was updated successfully, but these errors were encountered: