σ
@K7]c           @` s²   d  d l  m Z m Z m Z d  d l Z d  d l Z d  d l Z d  d l m Z d  d l m	 Z	 d  d l m
 Z
 d  d l m Z e j d e j  d   Z d	   Z d
   Z d S(   i    (   t   absolute_importt   divisiont   print_functionN(   t   binstar_upload(   t   ArgumentParser(   t   add_parser_channels(   t   apit   levelc      
   C` s¨  t  d d  } | j d d d d d d d	 d
 t | j d d d d t j d d	 d
 t | j d d d | j d d d | j d d d d d d
 g  d d | j d d d | j d d d | j d d t d
 d d d | j d d
 d  d d | j d d d  d! d
 d, d d" | j d# d d$ | j d% d d& d d' | j d( d d) | j d* d  d! d
 d- d d+ t |  | j |   }  | |  f S(.   Nt   descriptions  
Tool for building conda metapackages.  A metapackage is a package with no
files, only metadata.  They are typically used to collect several packages
together into a single package via dependencies.

NOTE: Metapackages can also be created by creating a recipe with the necessary
metadata in the meta.yaml, but a metapackage can be created entirely from the
command line with the conda metapackage command.
s   --no-anaconda-uploadt   actiont   store_falset   helps1   Do not ask to upload the package to anaconda.org.t   destt   anaconda_uploadt   defaults   --no-binstar-uploads   --tokens(   Token to pass through to anaconda uploads   --users7   User/organization to upload packages to on anaconda.orgs   --labelt   appendt   labelss1   Label argument to pass through to anaconda uploadt   names   Name of the created package.t   versions   Version of the created package.s   --build-numbert   typei    s,   Build number for the package (default is 0).s   --build-stringsB   Build string for the package (default is automatically generated).s   --dependenciess   -dt   nargst   *s   The dependencies of the package. To specify a version restriction for a
        dependency, wrap the dependency in quotes, like 'package >=2.0'.s   --homes!   The homepage for the metapackage.s	   --licenses   The license of the metapackage.t   license_names	   --summarys  Summary of the package.  Pass this in as a string on the command
        line, like --summary 'A metapackage for X'. It is recommended to use
        single quotes if you are not doing variable substitution to avoid
        interpretation of special characters.s   --entry-pointss  Python entry points to create automatically. They should use the same
        syntax as in the meta.yaml of a recipe, e.g., --entry-points
        bsdiff4=bsdiff4.cli:main_bsdiff4 will create an entry point called
        bsdiff4 that calls bsdiff4.cli.main_bsdiff4(). (    (    (	   R   t   add_argumentR   t   argparset   SUPPRESSt   intt   NoneR   t
   parse_args(   t   argst   p(    (    s?   lib/python2.7/site-packages/conda_build/cli/main_metapackage.pyR      sz    				
c         C` sV   t  |   \ } }  |  j j d  p9 |  j j d  p9 d } t j d | |  j  d  S(   Nt   channelt   channelst   channel_urls(    (   R   t   __dict__t   getR   t   create_metapackage(   R   t   _R!   (    (    s?   lib/python2.7/site-packages/conda_build/cli/main_metapackage.pyt   executev   s    *c           C` s   t  t j d  S(   Ni   (   R&   t   syst   argv(    (    (    s?   lib/python2.7/site-packages/conda_build/cli/main_metapackage.pyt   main|   s    (   t
   __future__R    R   R   R   t   loggingR'   t   conda_build.conda_interfaceR   R   R   t   conda_buildR   t   basicConfigt   INFOR   R&   R)   (    (    (    s?   lib/python2.7/site-packages/conda_build/cli/main_metapackage.pyt   <module>   s   	a	