Browse files

Build without filenames in Makefile.

  • Loading branch information...
rcrowley committed Jul 16, 2011
1 parent de0f0bf commit 8092bafa5f1e50c23590f3da21c4fe05dec4ce9e
@@ -22,26 +22,25 @@ clean:
install: install-lib install-man
- install -d $(DESTDIR)$(pydir)/
- install -m644 $(DESTDIR)$(pydir)/
- PYTHONPATH=$(DESTDIR)$(pydir) $(PYTHON) -mcompileall \
- $(DESTDIR)$(pydir)/
+ find cloudformation -type d -printf %P\\0 | xargs -0r -I__ install -d $(DESTDIR)$(pydir)/cloudformation/__
+ find cloudformation -type f -name \*.py -printf %P\\0 | xargs -0r -I__ install -m644 cloudformation/__ $(DESTDIR)$(pydir)/cloudformation/__
+ PYTHONPATH=$(DESTDIR)$(pydir) $(PYTHON) -mcompileall $(DESTDIR)$(pydir)/cloudformation
- install -d $(DESTDIR)$(mandir)/man7
- install -m644 man/man7/python-cloudformation.7 $(DESTDIR)$(mandir)/man7/
+ find man -type d -printf %P\\0 | xargs -0r -I__ install -d $(DESTDIR)$(mandir)/__
+ find man -type f -name \*.[12345678].gz -printf %P\\0 | xargs -0r -I__ install -m644 man/__ $(DESTDIR)$(mandir)/__
uninstall: uninstall-lib uninstall-man
- rm -f \
- $(DESTDIR)$(pydir)/ \
- $(DESTDIR)$(pydir)/cloudformation.pyc
- rmdir -p --ignore-fail-on-non-empty $(DESTDIR)$(pydir)
+ find cloudformation -type f -name \*.py -printf %P\\0 | xargs -0r -I__ rm -f $(DESTDIR)$(pydir)/cloudformation/__ $(DESTDIR)$(pydir)/cloudformation/__c
+ find cloudformation -depth -mindepth 1 -type d -printf %P\\0 | xargs -0r -I__ rmdir $(DESTDIR)$(pydir)/cloudformation/__ || true
+ rmdir -p --ignore-fail-on-non-empty $(DESTDIR)$(pydir)/cloudformation || true
- rm -f $(DESTDIR)$(mandir)/man7/python-cloudformation.7
- rmdir -p --ignore-fail-on-non-empty $(DESTDIR)$(mandir)/man7
+ find man -type f -name \*.[12345678].gz -printf %P\\0 | xargs -0r -I__ rm -f $(DESTDIR)$(mandir)/__
+ find man -depth -mindepth 1 -type d -printf %P\\0 | xargs -0r -I__ rmdir $(DESTDIR)$(mandir)/__ || true
+ rmdir -p --ignore-fail-on-non-empty $(DESTDIR)$(mandir) || true
build: build-deb build-pypi
@@ -80,6 +79,7 @@ deploy-pypi:
find man -name \*.ronn | xargs -n1 ronn \
--manual="python-cloudformation" --organization=DevStructure --style=toc
+ find man -name \*.[12345678] | xargs gzip
gh-pages: man
mkdir -p gh-pages
File renamed without changes.
@@ -1,77 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.TH "PYTHON\-CLOUDFORMATION" "7" "June 2011" "DevStructure" "python-cloudformation"
-\fBpython\-cloudformation\fR \- tools for creating CloudFormation templates
-import cloudformation
-import sys
-t = cloudformation\.Template()
-t\.Description = \'Demo of python\-cloudformation\.\'
- Description=\'Public IP address of DemoInstance\',
- Value={\'Fn::GetAtt\': [\'DemoInstance\', \'PublicIp\']})
- Description=\'DemoParam description\.\',
- Type=\'String\')
- Default=\'ami\-e2af508b\',
- Description=\'AMI to use for all EC2 instances\.\',
- Type=\'String\')
- Default=\'m1\.small\',
- Description=\'Instance type to use for all EC2 instances\.\',
- Type=\'String\')
- Properties={\'ImageId\': {\'Ref\': \'ImageId\'},
- \'InstanceType\': {\'Ref\': \'InstanceType\'},
- \'KeyName\': {\'Ref\': \'KeyName\'},
- \'SecurityGroups\': [{\'Ref\': \'DemoSecurityGroup\'}],
- \'UserData\': t\.ref_user_data({\'Ref\': \'DemoParam\'})},
- Type=\'AWS::EC2::Instance\')
- Properties={
- \'GroupDescription\': \'Unrestricted SSH and HTTP\.\',
- \'SecurityGroupIngress\': [{\'CidrIp\': \'0\.0\.0\.0/0\',
- \'FromPort\': \'22\',
- \'IpProtocol\': \'tcp\',
- \'ToPort\': \'22\'},
- {\'CidrIp\': \'0\.0\.0\.0/0\',
- \'FromPort\': \'80\',
- \'IpProtocol\': \'tcp\',
- \'ToPort\': \'80\'}]},
- Type=\'AWS::EC2::SecurityGroup\')
-\fBpython\-cloudformation\fR transforms Python source code representations of AWS CloudFormation templates into JSON\. It\'s most useful for automating tedious user data manipulation in its very rudimentary "templating language\."
-After constructing a \fBcloudformation\.Template\fR object there are two main classes of APIs available\. The first is a \fBdict\fR/\fBset\fR\-like API to \fBDescription\fR, \fBMappings\fR, \fBOutputs\fR, \fBParameters\fR, and \fBResources\fR\. \fBDescription\fR should be get and set as a string property\. The rest may be treated like dictionaries or sets via the \fBadd\fR method, which takes a \fBkey\fR and arbitrary keyword arguments\. These data structures will be faithfully reproduced in the JSON output\.
-EC2 user data is handled separately\. The \fBadd_user_data\fR method accepts a file\-like object which it reads, parses, and stores for later\. The parsing step is very rudimentary: it splits the input on "\fB____\fR"\. Later, the \fBref_user_data\fR method will replace the "\fB____\fR" markers with its positional parameters in the order they appear\. Use \fBref_user_data\fR as the value of the \fBUserData\fR key in the \fBProperties\fR dictionary of a \fBResource\fR with \fBType=\'AWS::EC2::Instance\'\fR\.
-Led Zeppelin \- "Night Flight"
-Richard Crowley \fIrichard@devstructure\.com\fR
-Blueprint I/O Server can create user data scripts for EC2 instance configuration\. See \fIhttp://devstructure\.com/docs/endpoints\.html#GET\-user\-data\fR for more information\.
Binary file not shown.

0 comments on commit 8092baf

Please sign in to comment.