conda-forge / libgpuarray-feedstock

A conda-smithy repository for libgpuarray.

About libgpuarray

Home: http://github.com/Theano/libgpuarray

Package license: ISC

Feedstock license: BSD-3-Clause

Summary: Library to manipulate arrays on GPU

Development: http://github.com/Theano/libgpuarray

Documentation: http://deeplearning.net/software/libgpuarray/

Current build status

Azure

Variant Status linux_64 osx_64 osx_arm64 win_64

Current release info

Name	Downloads	Version	Platforms

Installing libgpuarray

Installing libgpuarray from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge

Once the conda-forge channel has been enabled, libgpuarray can be installed with:

conda install libgpuarray

It is possible to list all of the versions of libgpuarray available on your platform with:

conda search libgpuarray --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by CircleCI, AppVeyor and TravisCI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating libgpuarray-feedstock

If you would like to improve the libgpuarray 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 conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/libgpuarray-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/number back to 0.

Feedstock Maintainers

• @abergeron

libgpuarray-feedstock's Issues

Building with an OpenCL BLAS

Am working on adding two OpenCL BLASes to conda-forge. In particular am adding clBLAS and CLBlast. IIUC libgpuarray can support one or the other. So am opening this issue to discuss how we handle building libgpuarray. With CPU BLAS support we have a selection package, which determines the CPU BLAS used by all packages. Perhaps a similar strategy makes sense here.

xref: conda-forge/staged-recipes#3190
xref: conda-forge/staged-recipes#3196
ref: https://github.com/conda-forge/blas-feedstock
ref: https://conda-forge.hackpad.com/BLAS-Numpy-Friends-86De62hoNdT

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender.

Rename the package to pygpu?

The name difference with the official conda package is causing some confusion amongst our users.

The problem is that many are doing conda install Theano pygpu and get Theano/python from conda-forge and pygpu/libgpuarray from official conda this way. This often results in a non-functional install, especially on windows.

Maybe we could rename this package to pygpu to avoid the confusion issues.

I'm not sure how such things are handled in conda-forge which is why I made an issue to see if that was possible.