Search results

zeromq-2.2.0-4.lbn13.x86_64

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialized messaging middle-ware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more. This package contains the ZeroMQ shared library.

zeromq-4.3.5-21.lbn36.x86_64

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialized messaging middle-ware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more. This package contains the ZeroMQ shared library.

zeromq3-3.2.2-2.lbn13.x86_64

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialized messaging middle-ware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more. This package contains the ZeroMQ shared library for versions 3.x.

zeromq3-3.2.5-1.lbn19.x86_64

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialized messaging middle-ware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more. This package contains the ZeroMQ shared library for versions 3.x.

zest.pocompile-1.3-2.lbn13.noarch

This package compiles po files. It contains a zest.releaser entry point and a stand-alone command line tool. Goal You want to release a package that has a locales dir (or locale, or something else as long as it has a LC_MESSAGES folder somewhere in it) with translations in .po files. You want to include the compiled .mo files in your release as well, but you do not want to keep those in a revision control system (like subversion) as they are binary and can be easily recreated. That is good. This package helps with that. Want .mo files? Add a MANIFEST.in file. When you use python setup.py sdist to create a source distribution, distutils (or setuptools or distribute or distutils2) knows which files it should include by looking at the information of the revision control system (RCS). This is why in the case of subversion you should use a checkout and not an export: you need the versioning information. (For other RCS or for subversion 1.7+ you currently need to install extra packages like setuptools-git.)

zest.pocompile-1.3-2.lbn19.noarch

This package compiles po files. It contains a zest.releaser entry point and a stand-alone command line tool. Goal You want to release a package that has a locales dir (or locale, or something else as long as it has a LC_MESSAGES folder somewhere in it) with translations in .po files. You want to include the compiled .mo files in your release as well, but you do not want to keep those in a revision control system (like subversion) as they are binary and can be easily recreated. That is good. This package helps with that. Want .mo files? Add a MANIFEST.in file. When you use python setup.py sdist to create a source distribution, distutils (or setuptools or distribute or distutils2) knows which files it should include by looking at the information of the revision control system (RCS). This is why in the case of subversion you should use a checkout and not an export: you need the versioning information. (For other RCS or for subversion 1.7+ you currently need to install extra packages like setuptools-git.)

zest.pocompile-1.4-1.lbn25.noarch

This package compiles po files. It contains a zest.releaser entry point and a stand-alone command line tool. Goal You want to release a package that has a locales dir (or locale, or something else as long as it has a LC_MESSAGES folder somewhere in it) with translations in .po files. You want to include the compiled .mo files in your release as well, but you do not want to keep those in a revision control system (like subversion) as they are binary and can be easily recreated. That is good. This package helps with that. Want .mo files? Add a MANIFEST.in file. When you use python setup.py sdist to create a source distribution, distutils (or setuptools or distribute or distutils2) knows which files it should include by looking at the information of the revision control system (RCS). This is why in the case of subversion you should use a checkout and not an export: you need the versioning information. (For other RCS or for subversion 1.7+ you currently need to install extra packages like setuptools-git.)

zest.releaser-3.43-1.lbn13.noarch

zest.releaser is collection of command-line programs to help you automate the task of releasing a software project. It's particularly helpful with Python package projects, but it can also be used for non-Python projects. For example, it's used to tag buildouts - a project only needs a version.txt file to be used with zest.releaser. It will help you to automate: * Updating the version number. The version number can either be in setup.py or version.txt. For example, 0.3.dev0 (current) to 0.3 (release) to 0.4.dev0 (new development version). * Updating the history/changes file. It logs the release date on release and adds a new section for the upcoming changes (new development version). * Tagging the release. It creates a tag in your version control system named after the released version number. * Uploading a source release to PyPI. It will only do this if the package is already registered there (else it will ask, defaulting to 'no'); the Zest Releaser is careful not to publish your private projects! It can also check out the tag in a temporary directory in case you need to modify it.

zest.releaser-6.13.5-1.lbn25.noarch

zest.releaser is collection of command-line programs to help you automate the task of releasing a software project. It's particularly helpful with Python package projects, but it can also be used for non-Python projects. For example, it's used to tag buildouts - a project only needs a version.txt file to be used with zest.releaser. It will help you to automate: * Updating the version number. The version number can either be in setup.py or version.txt. For example, 0.3.dev0 (current) to 0.3 (release) to 0.4.dev0 (new development version). * Updating the history/changes file. It logs the release date on release and adds a new section for the upcoming changes (new development version). * Tagging the release. It creates a tag in your version control system named after the released version number. * Uploading a source release to PyPI. It will only do this if the package is already registered there (else it will ask, defaulting to 'no'); the Zest Releaser is careful not to publish your private projects! It can also check out the tag in a temporary directory in case you need to modify it.

zest.releaser-6.13.5-1.lbn25.noarch

zest.releaser is collection of command-line programs to help you automate the task of releasing a software project. It's particularly helpful with Python package projects, but it can also be used for non-Python projects. For example, it's used to tag buildouts - a project only needs a version.txt file to be used with zest.releaser. It will help you to automate: * Updating the version number. The version number can either be in setup.py or version.txt. For example, 0.3.dev0 (current) to 0.3 (release) to 0.4.dev0 (new development version). * Updating the history/changes file. It logs the release date on release and adds a new section for the upcoming changes (new development version). * Tagging the release. It creates a tag in your version control system named after the released version number. * Uploading a source release to PyPI. It will only do this if the package is already registered there (else it will ask, defaulting to 'no'); the Zest Releaser is careful not to publish your private projects! It can also check out the tag in a temporary directory in case you need to modify it.