[FEATURE] Request for automating run_exports in meta.yaml

[akikuno]

Recently, it seems that the inclusion of run_exports in meta.yaml has become necessary.

I'm not sure how much demand there is for this feature outside of my own needs, but automating the inclusion of run_exports would be incredibly helpful in reducing errors.

Currently, I manually add the following run_exports to meta.yaml files generated by grakskull:

build:
  run_exports:
  - {{ pin_subpackage(name|lower, max_pin='x.x') }}

Here is an example:
https://github.com/bioconda/bioconda-recipes/blob/master/recipes/cstag/meta.yaml#L16

Thank you very much for your consideration.

[ocefpaf]

Hi @akikuno. Thanks for opening this issue. I have to confess that I don't understand your request. I may be missing something but that is not what run_exports was designed for. Maybe, if you want to control pure python packages that can install this you can use run_constraint instead?

Pinging @mbargull here b/c he is the only other bioconda person I know 😬

[akikuno]

@ocefpaf
Thank you for your comment.

I apologize for the confusion. I've recently been confronted with expectations regarding run_exports and run_constrained in Bioconda, and I admit I didn't fully grasp them.

Upon further research, it seems that the way these sections are written can vary depending on the package being developed. I'm now thinking that perhaps these are areas that should be manually edited.

In any case, grayskull is an incredibly useful tool, and I genuinely appreciate it. I wanted to take this opportunity to express my gratitude.