manifest: drop containernetworking-plugins and podman-plugins

[gursewak1997]

Since podman is dropping support for CNI networking entirely we can drop containernetworking-plugins and podman-plugins. Podman stopped shipping podman-plugins rpm with the Podmanv5. Subsequently, we wouldn't need containernetworking-plugins as it is just libraries for writing CNI plugins.
Ref: coreos/fedora-coreos-tracker#1629 (comment)

[jlebon]

This needs to be made conditional on Fedora 40. Or in other words, you would move the containernetworking-plugins and podman-plugins bits to a separate manifest, and add a conditional include for f39 for that manifest. Grep for conditional-include to see examples of this.

Also /cc @mheon to sanity-check: there's no point in having these packages in f40, right?

[mheon]

Podman-plugins we definitely have no further use for. Containernetworking-plugins is still used by CRI-O but I'm not sure how that ships in Fedora

[jlebon]

Podman-plugins we definitely have no further use for. Containernetworking-plugins is still used by CRI-O but I'm not sure how that ships in Fedora

Ack, thanks.

Looks like the CRI-O in Fedora Suggests it. Since CRI-O currently needs to be layered separately, I think we could also have any users doing that also layer this if they need it. We should mention it as part of our f40 communications.

[dustymabe]

one suggestion. otherwise LGTM

[dustymabe]

podman v5 will never go to F39.

Suggested change

	# Delete this file once Podman v5 releases to f39
	# Delete this file once we are on Podman v5 everywhere.
	# i.e. We have moved past F39.

[dustymabe]

LGTM