Wildcard package spec support

[bqv]

When trying to use cave on my system, which has extensive configs, i see errors like:

$ cave resolve -x paludis                                                                                                                                                                                   
cave@1674740539: [WARNING portage_environment.dodgy] Use of Portage configuration files will lead to sub-optimal performance and loss of functionality. Full support for Portage configuration formats is not guarant
eed; issues should be reported via trac.

Error:
  * In program cave resolve -x paludis:
  * When making environment from specification '':
  * When creating PortageEnvironment using config root '':
  * When loading '/etc/portage/package.accept_keywords':
  * When loading '/etc/portage/package.accept_keywords/overlay':
  * When parsing user package dep spec '*/*::qt':
  * When parsing generic package dep spec '*/*::qt':
  * Wildcard '*' not allowed (paludis::PackageDepSpecError)

I would remove wildcards from my config, but that would be most of my config!

How hard would it be to add support for these?

[negril]

My /etc/paludis/keywords.conf.d/00_keywords.conf has this in it:

*/*::steam-overlay *

Which works as expected.

So it might just be an issue using the portage configuration files.

Is switching to the paludis config format viable for you? The old script that does that is not perfect but gives you a working baseline.

[bqv]

Hmm. Where is said script, I'm happy to try it :)

That said, surely if it is possible, then implementing it for portage config should be possible?

[negril]

See https://paludis.exherbo.org/overview/gettingstarted.html under "Automatically migrating".

It might just be a config setting somewhere but we'd have to check. As far as I remember that code is rarely used so you might run into more problems.

[bqv]

well, that does work, thanks! I would prefer to not maintain two versions of the same config though