Feedstock license: BSD-3-Clause
Home: /~https://github.com/ramonaoptics/spyder-desktop-feedstock
Package license: BSD-3-Clause
Summary: Desktop launchers for spyder when installed in linux
This will create a desktop launcher for Spyder. The launcher will override other launchers.
| Azure |
|
| Name | Downloads | Version | Platforms |
|---|---|---|---|
 |
 |
 |
 |
Installing spyder-desktop from the ramonaoptics channel can be achieved by adding ramonaoptics to your channels with:
conda config --add channels ramonaoptics
conda config --set channel_priority strict
Once the ramonaoptics channel has been enabled, spyder-desktop can be installed with conda:
conda install spyder-desktop
or with mamba:
mamba install spyder-desktop
It is possible to list all of the versions of spyder-desktop available on your platform with conda:
conda search spyder-desktop --channel ramonaoptics
or with mamba:
mamba search spyder-desktop --channel ramonaoptics
Alternatively, mamba repoquery may provide more information:
# Search all versions available on your platform:
mamba repoquery search spyder-desktop --channel ramonaoptics
# List packages depending on `spyder-desktop`:
mamba repoquery whoneeds spyder-desktop --channel ramonaoptics
# List dependencies of `spyder-desktop`:
mamba repoquery depends spyder-desktop --channel ramonaoptics
If you would like to improve the spyder-desktop recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
ramonaoptics channel, whereupon the built conda packages will be available for
everybody to install and use from the ramonaoptics channel.
Note that all branches in the ramonaoptics/spyder-desktop-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.
In order to produce a uniquely identifiable distribution:
- If the version of a package is not being increased, please add or increase
the
build/number. - If the version of a package is being increased, please remember to return
the
build/numberback to 0.