Add output gst-rtsp-server to gstreamer feedstock

[FlyingSamson]

Guidelines for marking packages as broken:

• We prefer to patch the repo data (see here)
  instead of marking packages as broken. This alternative workflow makes environments more reproducible.
• Packages with requirements/metadata that are too strict but otherwise work are
  not technically broken and should not be marked as such.
• Packages with missing metadata can be marked as broken on a temporary basis
  but should be patched in the repo data and be marked unbroken later.
• In some cases where the number of users of a package is small or it is used by
  the maintainers only, we can allow packages to be marked broken more liberally.
• We (conda-forge/core) try to make a decision on these requests within 24 hours.

What will happen when a package is marked broken?

• Our bots will add the broken label to the package. The main label will remain on the package and this is normal.
• Our bots will rebuild our repodata patches to remove this package from the repodata.
• In a few hours after the anaconda.org CDN picks up the new patches, you will no longer be able to install the package from the main channel.

Checklist:

• I want to mark a package as broken (or not broken):

  • Added a description of the problem with the package in the PR description.
  • Pinged the team for the package for their input.

• I want to archive a feedstock:

  • Pinged the team for that feedstock for their input.
  • Make sure you have opened an issue on the feedstock explaining why it was archived.
  • Linked that issue in this PR description.
  • Added links to any other relevant issues/PRs in the PR description.

• I want to request (or revoke) access to an opt-in CI resource:

  • Pinged the relevant feedstock team(s)
  • Added a small description explaining why access is needed

• I want to copy an artifact following CFEP-3:

  • Pinged the relevant feedstock team(s)
  • Added a reference to the original PR
  • Posted a link to the conda artifacts
  • Posted a link to the build logs

• I want to add a package output to a feedstock:

  • Pinged the relevant feedstock team(s)
  • Added a small description of why the output is being added.

This PR strives to add the gst-rtsp-server plugin to the gstreamer feedstock.

ping @conda-forge/gstreamer

[hmaarrfk]

i would like to hear from the present maintainers of the gstreamer stack that they do in fact want to add a separate package for this instead of folding it in to one of the existing packages.

[tjwilli58]

i would like to hear from the present maintainers of the gstreamer stack that they do in fact want to add a separate package for this instead of folding it in to one of the existing packages.

The more I think about it, I think that this should be in its own feedstock, along with the ones you have listed in conda-forge/gstreamer-feedstock#146

Also conda-forge/gstreamer-feedstock#170 (comment)

How do you do that?

[hmaarrfk]

Make a PR to: https://github.com/conda-forge/staged-recipes

[tjwilli58]

I was thinking about doing that. I never did one before, so I need to read up on that.

[hmaarrfk]

please open the PR again when you find it appropriate.

[tjwilli58]

@hmaarrfk , which PR are you referring to? gst-rtsp-server has its own feedstock now. I'm confused.

Are you talking about these issues?
conda-forge/gst-rtsp-server-feedstock#8
conda-forge/gst-rtsp-server-feedstock#4

I must admit that I forgot about them and need to revisit.

[hmaarrfk]

I just mean in general.

Seems like this got forgotten and I wanted to cleanup.

But if you think this is still relevant. Do you want me to merge this?

[tjwilli58]

I guess I don't understand what this PR does. Does this add gst-rtsp-server to the gstreamer-feedstock? Why? It already has its own feedstock.

[tjwilli58]

I finally asked CoPilot what

action: add_feedstock_output
feedstock_to_output_mapping:
  - gstreamer: gst-rtsp-server

does.

The bot will:

Locate the gstreamer feedstock.

Modify its recipe structure.

Add a new output section for gst-rtsp-server.

Trigger CI to build/publish that output.

It’s essentially a structured request for feedstock surgery.

I don't see a need to add this to the gstreamer feedstock. The existing 3 outputs

• gstreamer
• gst-plugins-base
• gst-plugins-good

are sufficient.