-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathmeta.yaml
128 lines (104 loc) · 4.81 KB
/
meta.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
package:
name: pymecs # lower case name of package, may contain '-' but no spaces
version: 1.0 # version of package. Should use the PEP-386 verlib
# conventions. Note that YAML will interpret
# versions like 1.0 as floats, meaning that 1.0 will
# be the same as 1. To avoid this, always put the
# version in quotes, so that it will be interpreted
# as a string.
# The version cannot contain a dash '-' character.
source:
path: .
build:
# The build number should be incremented for new builds of the same version
number: 0 # (defaults to 0)
#string: abc # (defaults to default conda build string plus the build
# number)
# The build string cannot contain a dash '-' character
# Optional Python entry points
entry_points:
# This creates an entry point named bsdiff4 that calls
# bsdiff4.cli.main_bsdiff4()
#- bspatch4 = bsdiff4.cli:main_bspatch4
# If osx_is_app is set, entry points will use python.app instead of
# python in Mac OS X
osx_is_app: yes # (defaults to no)
# See the Features section below for more information on features
# Defines what features a package has
#features:
# - feature1
# Indicates that installing this package should enable (track) the given
# features. It is generally a good idea to use a separate metapackage to
# track a feature, which does not have the feature. See the Features
# section below for more information about features.
#track_features:
# - feature2
# Preserve the Python egg directory. This is needed for some packages
# that use setuptools specific features.
#preserve_egg_dir: yes # (default no)
# A list of globs for files that should not be linked (soft or
# hard). They will always be copied.
#no_link:
# - bin/*.py # Don't link any .py files in bin/
# Used instead of build.sh or bld.bat. For short build scripts, this can
# be more convenient. You may need to use selectors (see below) to use
# different scripts for different platforms.
#script: python setup.py install
# Set which RPATHs are used when making executables relocatable. This
# currently only works on Linux. The default is lib/
#rpaths:
# - lib/
# - lib/R/lib/
# Force files to always be included, even if they are already in the
# environment from the build dependencies. This is needed, for instance,
# to create a recipe for conda itself.
#always_include_files:
# - bin/file1
# - bin/file2
#########################################################################
# binary_relocation, has_prefix_files, binary_has_prefix_files, and #
# detect_binary_files_with_prefix may be required to relocate files #
# from the build environment to the installation environment. See #
# "Making Packages Relocatable" below. #
#########################################################################
# Whether binary files should be made relocatable using install_name_tool
# on OS X or patchelf on Linux.
binary_relocation: true # (defaults to true)
# Binary files may contain the build prefix and need it replaced with the
# install prefix at installation time. Conda can automatically identify
# and register such files:
detect_binary_files_with_prefix: true # (defaults to false)
# or you may elect to specify such files individually:
#binary_has_prefix_files:
# - bin/binaryfile1
# - lib/binaryfile2
# Text files (containing no NULL bytes) may contain the build prefix and
# need it replaced with the install prefix at installation time. Conda
# will automatically register such files. Binary files that contain the
# build prefix are generally handled differently (see
# binary_has_prefix_files or detect_binary_files_with_prefix), but there
# may be cases where such a binary file needs to be treated as an
# ordinary text file, in which case they need to be identified:
#has_prefix_files:
# - bin/file1
# - lib/file2
# the build and runtime requirements. Dependencies of these requirements
# are included automatically.
requirements:
# Packages required to build the package. python and numpy must be
# listed explicitly if they are required.
build:
- python
- python-microscopy
# Packages required to run the package. These are the dependencies that
# will be installed automatically whenever the package is installed.
# Package names should be any valid conda spec (see "Specifying versions
# in requirements" below).
run:
- python 2.7
- python-microscopy >=17.10.24
- statsmodels
about:
home: http://soellerlab.ex.ac.uk/pages/software.html
license: GPL
summary: Tools to extend the PYME distribution with plugins and other modules