Vikraman Choudhury

Changing it in the master repo is a major breaking change. I suggest you change the property name to something else in a personal fork for now.

I would like to propose the following feature: ``` puppet package_set { 'foo': ensure => installed } ``` will ensure that `@foo` is present in `world_sets`. ``` puppet package_set {...

This appears to be a limitation in the `parsedfile` provider: https://projects.puppetlabs.com/issues/6628

I believe this is a limitation of the `parsedfile` provider. Moving to `puppet-filemapper` will fix all these issues. http://adrienthebo.github.io/puppet-filemapper/#Removing_empty_files

`package_env` is already implemented. For `portage::env`, just use a `file` resource?

I tried implementing what op suggested with `concat` but it doesn't work if we set multiple `portage::env` resources to have the same `target`. We could instead have a list of...

Installing in two or more different slots using `portage::package` is not possible yet. We need to patch the upstream package provider to query slots through `eix`.

This will be a lot easier if the upstream provider supports slots: https://github.com/puppetlabs/puppet/pull/2649