Consider adding pixi install commands to feedstock README template

[matthewfeickert]

Comment:

At the moment the feedstock README template gives instructions for how to install and search for conda-forge packages with conda and mamba

conda-smithy/conda_smithy/templates/README.md.tmpl

Lines 219 to 254 in 73c3564

	Once the `{{ channel_with_label }}` channel has been enabled, `{{ ', '.join(outputs) }}` can be installed with `conda`:
	```
	conda install {{ ' '.join(outputs) }}
	```
	or with `mamba`:
	```
	mamba install {{ ' '.join(outputs) }}
	```
	It is possible to list all of the versions of `{{ outputs[0] }}` available on your platform with `conda`:
	```
	conda search {{ outputs[0] }} --channel {{ channel_with_label }}
	```
	or with `mamba`:
	```
	mamba search {{ outputs[0] }} --channel {{ channel_with_label }}
	```
	Alternatively, `mamba repoquery` may provide more information:
	```
	# Search all versions available on your platform:
	mamba repoquery search {{ outputs[0] }} --channel {{ channel_with_label }}
	# List packages depending on `{{ outputs[0] }}`:
	mamba repoquery whoneeds {{ outputs[0] }} --channel {{ channel_with_label }}
	# List dependencies of `{{ outputs[0] }}`:
	mamba repoquery depends {{ outputs[0] }} --channel {{ channel_with_label }}
	```

I think it would be really nice to also add instructions for how to install and search using pixi (https://pixi.sh/). pixi has become the default way I interact with conda-forge packages for all my projects except when external legacy situations from my collaborators currently make it infeasible, so I'd be interested in it getting copy-pasteable commands on conda-forge.

I'm not sure if this is the correct place to discuss this, but as this is the repository that builds / rerenders feedstocks I thought I'd start here.

[baszalmstra]

See: #1856

[matthewfeickert]

Thanks @baszalmstra! 👍 I had only checked the open and closed Issues and not the PRs so I missed this.

[matthewfeickert]

👋 @xhochy @isuruf, I know that you're busy and this is a low priority item compared to most other things happening for the core team, but as you've given reviews of PR #1856 would you be willing to weigh in here (or on PR #1856 again) on the possibility of this?

[isuruf]

Maybe we should have a page in our website on different ways of installing conda-forge packages and link to it from the feedstock. It's not going to be feasible to add more and more tools.

[matthewfeickert]

Maybe we should have a page in our website on different ways of installing conda-forge packages and link to it from the feedstock.

Would that mean that there would be no install instructions at all on the feedstocks? That seems strange to me.

[isuruf]

The website would have the install instructions there for the packages.

[matthewfeickert]

The website would have the install instructions there for the packages.

Yeah, I understand, but still seems a bit strange when Markdown is collapsable (e.g. #1856 (comment)). That being said, I think having install instructions that don't favor one tool in particular on a secondary site it still better than having nothing at all.