General discussion about Chef

[chef] RFC: CHEF-425 Gentoo package names


Chronological Thread 
  • From: Kenneth Kalmer < >
  • To: chef < >
  • Subject: [chef] RFC: CHEF-425 Gentoo package names
  • Date: Thu, 4 Feb 2010 12:30:09 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=Ral0eercE69jm6UoNIQgR8kCMoUWAOr5+2fBizOqV+znSlPZULpXnurAH1D867xRfP +SkP2MpaGiSR/qdDhFQ8rBskUE7LRmjrchX4vlwc2+wP383caHVSByUrpKIJWGn73tIH WxVCNhg51SAkZlmlZg4NjWgQrND7YVk1d2bbo=
Hi everyone

Ticket: http://tickets.opscode.com/browse/CHEF-425
Commits: http://github.com/kennethkalmer/chef/commit/8df3958 & http://github.com/kennethkalmer/chef/commit/3abe57

The issue is when providing package names to the Gentoo package provider without including a category name, which causes it to re-emerge installed packages over and over again. After applying some thought to it (and reviewing the code) it became obvious that one needs to provide a proper 'atom' to the package resource.

The first commit simply logs a warning for the chef user, alerting them that the atom isn't correct.

The second commit applies some voodoo to infer the possible category name for portage. If multiple categories are inferred, no assumptions are made, keeping ambiguous package names and letting emerge fail. However, if only a single category is found then the package name is updated to have this category name.

Please have a look and let me know what you think. I can understand the inferring code can be too much, hence two separate commits. At the very least the logging patch should be accepted.

Can I start a new page on the wiki detailing 'gotchas' for Gentoo? I'd like to ensure Gentoo users can enjoy chef without bumping their heads on small things like this.

Best

--
Kenneth Kalmer
">
http://opensourcery.co.za
@kennethkalmer

Archive powered by MHonArc 2.6.16.

§