[weasel-commit] Source: rmake=2.0.1-1.1.8
- From: rbuilder@xxxxxxxxx
- To: weasel-commit@xxxxxxxxxxxxx
- Date: Wed, 06 Jan 2010 12:43:33 -0500
================================
rmake:source=2.0.1-1.1.8 (previous: 2.0.1-1.1.7)
cvc rdiff rmake -1
/conary.rpath.com@rpl:devel//2-devel//weasel.rpath.org@wgl:3-devel/2.0.1-1.1.8
================================
2.0.1-1.1.8 Filip Brcic (brcha@xxxxxxx) Wed Jan 6 12:43:24 2010
added metadata
rmake.recipe: changed
Index: rmake.recipe
====================================================================
contents(size sha1)
inode(mtime)
--- rmake.recipe
/conary.rpath.com@rpl:devel//2-devel//weasel.rpath.org@wgl:3-devel/2.0.1-1.1.7
+++ rmake.recipe
/conary.rpath.com@rpl:devel//2-devel//weasel.rpath.org@wgl:3-devel/2.0.1-1.1.8
@@ -15,6 +15,25 @@
'conary-repository:python', 'python:devel',
]
+ shortDesc = 'rMake chroot build environment'
+ longDesc = """
+rMake handles build jobs using the conary packaging system. rMake
+automatically creates a fresh clean build chroot with everything a
+package needs to build according to its specific build
+requirements. Before rMake, you had to install the right software on
+your system in order to use "cvc cook" to build a package.
+
+There are currently two major components to rMake: the rMake Server
+and the rMake command line. The rMake Server runs as a daemon on your
+system. It accepts rMake build jobs, creates build environments,
+performs builds, and so on. The rMake command line controls the
+server. Use it to create new build jobs, view a list of jobs, view
+status and logs, and commit the resulting builds back to a Conary
+repository.
+"""
+ url = 'http://wiki.conary.com/'
+ licenses = [ 'CPL-1.0' ]
+ categories = [ 'System/Development' ]
def setup(r):
r.setDefaultPython()
Committed by: brcha
Other related posts:
- » [weasel-commit] Source: rmake=2.0.1-1.1.8 - rbuilder
