1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
== PPA Availability ==
There is a ppa maintained at
https://launchpad.net/~awstools-dev/+archive/awstools
That contains development versions of the package, and backports to stable
releases.
== Executing Scripts ==
When patches are applied (quilt push -a), the scripts in ./bin can be run in
place.
In order to do so, you need to set AWS_ELB_HOME=<top_level_dir>, and the
scripts must be made executable. The scripts are not executable in the source
package because the original source comes froma .zip file, which does not (can
not) contain the correct permissions.
http://ec2-downloads.s3.amazonaws.com/AutoScaling-2011-01-01.zip
== Version Number ==
The zip files available for download in the s3 bucket at
http://ec2-downloads.s3.amazonaws.com/ are named like
AutoScaling-2011-01-01.zip
while the contents have a top level directory like:
AutoScaling-1.0.61.0
These also match up with the output of as-version, which reports something like
Amazon AutoScaling CLI version 1.0.61.0 (API 2011-01-01)
There is no obvious way to convert download file name to version other than
downloading and listing contents (unzip -l).
== Upstream Source / Uscan ==
The upstream does not provide any parsable content to see the lastest release.
As a result, there is no debian/watch file. In order to make it easier to
check upstream source, there is a utility included in debian/upstream-check
that can be executed with './debian/rules upstream-check'.
A better solution to this would be to add support to uscan for parsing the
output of http://s3.amazonaws.com/rds-downloads/ .
Debian Bug 630756 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630756
Ubuntu Bug 798293 : http://bugs.launchpad.net/bugs/798293
Note, for Auto Scaling tools, due to the naming of the zip files
(described above in 'Version Number' section), the s3 support to uscan would
not be sufficient.
== Makefile ==
There is no make file included in the original source distribution.
I have included one here in first of the debian/patches/series.
It handles 'make' and 'make install'.
== Man pages ==
Man pages are generated from the '--help'. Rather than 'help2man', a utility
script is provided in debian/xhelp2man. This makes use of the usage output
and a manually maintained file debian/name2desc.
The man pages can be created with 'make man'
name2desc is manually maintained. It was originally created with:
for f in man/*.usage; do
n=${f%.usage}; n=${n##*/};
while read line; do [ "${line}" = "DESCRIPTION" ] && read desc && break;
done < "${f}";
printf "%s\t%s\n" "${n}" "${desc}"; done > debian/name2desc
== java system dependencies ==
The upstream "source" comes with several .jar files included (see lib/*.jar).
In order to both reduce the download size of the binaries and promote use
of common java libraries provided in usr/share/java, those libraries are not
included in the binary package.
Deciding which of the lib/*.jar files are included is maintained through 'make'.
On 'make install', the file debian/shared-java-libs is read. Each line in
that file lists a file in lib/, the Ubuntu package that provides the necessary
jar, and the name of the file in /usr/share/java that needs to be added to the
classpath.
Currently that list needs to be manually synced to the dependencies in
debian/control.
== Testing ==
debian/README.example contains an example of how to test some function of the
package.
|
