Issue #7719 has been updated by Nigel Kersten. Status changed from Needs Decision to Rejected
I'm rejecting this specific implementation, but there is work we'd like to do in the general area to make package dependencies in modules easier. ---------------------------------------- Feature #7719: Modules should "just work" with apt, yum, pkgdmg and pkgadd https://projects.puppetlabs.com/issues/7719 Author: Jeff McCune Status: Rejected Priority: Normal Assignee: Nigel Kersten Category: Target version: Affected Puppet version: Keywords: apt yum package module re-use reuse usability repository Branch: # Overview # It is difficult to write re-usable modules which install packages not available in the OS distribution by default. Puppet modules almost always need to install packages. Currently, packages are expected to be available in whatever provider is enabled on the Puppet Agent for the package resource. This makes it difficult to install software not already provided by the OS distribution. As an example, MCollective provides packages at [http://www.puppetlabs.com/downloads/mcollective/](http://www.puppetlabs.com/downloads/mcollective/) but these packages are not available in most OS distributions, and those that are likely lag behind the most recently available versions. # Expected Behavior # When I install the puppet module to manage mcollective, the software should be available to my Debian and RedHat based systems. I should not need to take additional steps to setup an apt or yum repository and configure my puppet managed nodes to use these online repositories. This should automatically happen for me. # Suggestions # The following platforms support package installation via HTTP in some form or another. I think they have good coverage across the platforms Puppet is used on and are a good start: * Yum (RedHat Enterprise Linux, OEL, CentOS) * Apt (Debian, Ubuntu) * Solaris 10 (dpkg can install directly from an http:// URL) * Mac OS X (The pkgdmg provider wirks with http:// URL's) # Potential Solutions # We could possibly include a packages/ sub directory of each module where each sub directory is a repository. e.g. [modulepath]/mcollective/packages/ * yum/redhat/5/x86_64/repodata/ * yum/centos/5/i386/repodata/ * yum/sles/10/x86_64/repodata/ * apt/lucid/amd64/Packages.gz * apt/squeeze/amd64/Packages.gz * etc... The Puppet Master could then make these packages available as a remote HTTP repository. Puppet in stand alone mode could automatically configure local file:/// based repositories for these directories. -- Jeff McCune Puppet Labs @0xEFF -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
