Meta-package hogging package name for project

Linking related proposal that would prevent this from being an ongoing issue 🌱 Change how modules and submodule dependencies are handled to have more consistent namepsaces [DRAFT]. Active

This is by design to prevent a new module from overriding a component of another project. In some cases, it is possible to get the package names reset. In the meantime, drupal/graphql_compose_fragments-graphql_compose_fragments is correct, Compose package names do not always match project names.

Considering that I am the author of both modules, perhaps it could be taken into consideration:

- the meta package didn't work as desired
- there was no stable release including the sub module
- the sub module no longer exists

And now it’s causing unwanted side effects.

Is it possible to remove the meta package? Or rename it to free up the normal package name?

🙏

I have swapped the package namespaces around - watch out for support requests related to the change.

• https://www.drupal.org/project/graphql_compose →
  • Old submodule namespace: graphql_compose_fragments
  • New submodule namespace:graphql_compose-graphql_compose_fragments
• https://www.drupal.org/project/graphql_compose_fragments →
  • Old package namespace:graphql_compose_fragments-graphql_compose_fragments
  • New package namespacegraphql_compose_fragments

Automatically closed - issue fixed for 2 weeks with no activity.