portage provider in Gentoo reinstalls the packages over and over again; does not matter if :install or :upgrade is used.

0.7.12

I can confirm this is still the case with chef 0.7.16, will take a look into it...

Kenneth,

Technically is related to the actual "package" statements in the cookbooks actually, as you would need to change

package "sudo" do
action :upgrade
end

For Gentoo, it needs to be;

package "app-admin/sudo" do
action :upgrade
end

the portage provider needs the "relative path" to find the sudo cookbook (not sure if that's the right phrase).

Scott,

After investigating the Portage package provider's code I've noted this behavior.

I've assigned the ticket to myself cause I feel there are a few possible things here that can be improved:

1. At the very least log a message to warn users when the package name misses the category
2. Try to resolve the category automatically from portage

Hoping at least the logging patch would make it back in

Logging commit in -> http://github.com/kennethkalmer/chef/commit/8df3958b04297be74a3ab4497b727c67d076af35

I made the log level info, since it is impossible to stub the warn level. Any workaround would be greatly appreciated. Continuing with category resolution...

Inferring category completed -> http://github.com/kennethkalmer/chef/commit/3abe575

The expectations on the logging is commented out since I cannot get them to work accurately :/

Testing this live to see how it behaves, feedback welcome.

ctennis & haloway gave this a glance over and both think it looks good.

Pull request sent for http://github.com/kennethkalmer/chef/tree/CHEF-425

I'm resolving this ticket, as it has patches attached that fast forward cleanly. Investigating whether this is still an issue with Gentoo, and we just missed this ticket.

I'm going to -1 this

Basically the problem as I see it with this is there's a possibility of package names being in multiple categories, and it's much easier to stick to using the Gentoo way of doing dev-vcs/git instead of just "git". It's nice for someone new to Chef and Gentoo to use package "apache2" but with Gentoo they'll likely want to change use flags and update /etc/portage/package.use so it does not break outside of chef either.

See previous comment.

Closing this ticket as won't fix... I reported it, so I can take it back... Great idea, it's just that portage doesn't always keep the package names non-disruptive at times as well as package names arn't always the same elsewhere.

It's just easier to either add a case block to do different with Gentoo in cookbooks or just update them and manage them yourself with the fully qualified package name.