Feature itself shouldn't be listed amongst its possible dependencies

I am not seeing this on any of my test sites. Are you sure it's not something special to your feature or that maybe you have another contrib module messing this up? Otherwise post a specific example of a feature that has this problem on a clean Drupal site.

I've seen this

semi related #2009386: Creating permissions inside a feature makes the feature dependent on itself #2029247: Feature added itself as a dependency ... can never be enabled

http://gyazo.com/c034e1f37d6e502bfb879e71eabf93d8 2.x on fresh drupal install

with tests

Committed to 69df8e1 (and fixed 2 whitespace errors in patch)

This patch actually causes issues with Entity API by changing the interface of the hook_features_export_options() function. I think this needs to be reverted and a better solution found. I'd rather not break compatibility with other modules this close to a Features 2.0 release even if Entity API shouldn't technically be adding it's own arguments to our API functions. See #2104245: Error - Unsupported operand types in sites/all/modules/entity/entity.features.inc.

So I misunderstood the original problem. I thought the feature itself was being checked automatically. The fact that it is listed as a possible dependency makes this a much less serious issue. Definitely going to revert this given the issue with Entity API. Let's try to find a different approach for this issue.

There's a function that is being called during depedencies_features_export that should be called at the end instead that does various cleanup

edit: ignore this comment, was thinking of a different issue

Postponing this until Features 2.1 and after Entity API has released a fix so this doesn't break in the future.

Could this be a solution to this issue?

Thanks :-)

re-rolled #11 against 7.x-2.10