trigger rebuild after package_* addition/edit

[tampakrap]

Currently I have implemented some code in portage::package in my fork to rebuild every time one of the package_* entries are touched. It would be better though if we add a new parameter in the provider, so we can do something like:

package_keywords { 'app-admin/puppet':
  keywords => '~x86',
  target => 'puppet',
  rebuild => true,
}

Default value should be false, in order to avoid useless rebuilds
The command that should be triggered is /usr/bin/emerge -u1 --changed-use ${name}

[adrienthebo]

👍 from me, will look at this more closely tonight.

[adrienthebo]

If this is going to be behavior injected into the provider then it's going to need more work than I initially considered. This would require that package_* types are always run before the associated packages and can trigger a reinstallation/rebuild, and I don't know how that would work on a provider level.

[tampakrap]

No, you are wrong. You just need to run the command I gave in the summary, no need to check if the package is there or whatever. The command there will take care everything. I have implemented that behavior in portage::package already and it works, but the problem there is that the command executes max 4 times (for each package_* entry) if all of them are assigned. Having this in provider level will solve the problem, as I will be able in portage::package to trigger the rebuild after all of those entries are filed, without checking order or dependencies between them. Plus it would be useful to have this one in cases where only a package_* type is used, without involving portage::package at all.