{ "info": { "author": "Kevin Carter", "author_email": "kevin.carter@rackspace.com", "bugtrack_url": null, "classifiers": [ "Development Status :: 5 - Production/Stable", "Intended Audience :: Developers", "Intended Audience :: Information Technology", "Intended Audience :: System Administrators", "License :: OSI Approved :: Apache Software License", "Operating System :: OS Independent", "Programming Language :: Python :: 2.6", "Programming Language :: Python :: 2.7", "Topic :: Software Development :: Libraries :: Python Modules", "Topic :: Utilities" ], "description": "Yet Another Python Repo Tool\n############################\n:date: 2013-09-05 09:51\n:tags: python, github, pip, pypi\n:category: \\*nix\n\n\nGeneral Overview\n----------------\n\nYaprt is a tool built to turn Python source code into a python wheels. While that not all that remarkable yaprt goes a bit further. The idea behind yaprt is to allow deployers to maintain lots of diverse projects in different repositories and turn source code into distributable python packages with minimal effort while maintaining dependencies and requirements across the various projects without finding duplicate packages and disjointed versions in what should be a stable deployment.\n\nYaprt has lots of functionality though has a simple cli interface. For everything yaprt can do please review ``yaprt --help``. Additionally all of the sub-commands have more information regarding options that are unique to the individual sub-command. These options can be viewed via ``yaprt sub-command --help``.\n\n\nExample Usage\n-------------\n\nThe commands listed regarding the functionality of yaprt assume that you will have the following directory structure created within your host.\n\n.. code-block:: bash\n\n mkdir -p /var/www/repos/ ## Main repo directory\n mkdir -p /var/www/repos/os-releases ## Location where symlinked wheels will exist\n mkdir -p /var/www/repos/pools ## Location where wheels will exist\n mkdir -p /var/www/repos/reports/ ## Location where report files will exist\n mkdir -p /var/www/repos/repos-file ## Location where requirement files will exist\n\n\nIn the basic example I'm going to assume that you have some ``repo_file.txt`` on your system and it has a bunch of git repos within it. In my example I will be creating a report targeting OpenStack services and clients for the latest *stable/juno* and will create all of the python wheels for use in my local index.\n\n.. code-block:: bash\n\n cat > /var/www/repos/repos-file/openstack-repos-file.txt<