OLD | NEW |
| (Empty) |
1 Package Generation Notes for gsutil | |
2 | |
3 Gsutil can be distributed in one of three ways: | |
4 | |
5 1. legacy mode - User unpacks archive file into a private directory tree | |
6 and maintains his/her own private copy of gsutil, boto, etc. This is the | |
7 only supported installation mode for Windows users. | |
8 | |
9 2. enterprise mode - User unpacks the gsutil archive file and runs | |
10 'python setup.py install' (as root), which installs everything into | |
11 a shared directory tree (/usr/share/gsutil) with a symlink from | |
12 /usr/bin/gsutil to /usr/share/gsutil/gsutil to provide easy access to | |
13 the shared gsutil command. In enterprise mode, the software gets installed | |
14 in one shared location, which makes it easier to install, update and | |
15 manage gsutil for a community of users. | |
16 | |
17 NOTE: Enterprise mode (installing gsutil via setup.py) is no longer | |
18 officially supported - unpacking the zip file into a directory is the | |
19 preferred method for installing gsutil for both shared and private | |
20 configurations. | |
21 | |
22 3. rpm mode - User installs the gsutil rpm package file on a Red Hat | |
23 Linux system using the rpm command. The resulting installation image | |
24 looks precisely the same as the results of installing with enterprise | |
25 mode, i.e. a shared directory tree (/usr/share/gsutil) with a symlink | |
26 from /usr/bin/gsutil. rpm mode is intended for enterprises that want | |
27 a stable release that does not necessarily contain the latest changes. | |
28 | |
29 All three modes derive their inventory from a common text file called | |
30 MANIFEST.in. If you want to add one or more new files or directories, | |
31 you only need to edit that one file and all three installation modes | |
32 will automatically inherit the change(s). | |
33 | |
34 GENERATING PACKAGE FILES | |
35 | |
36 First update the VERSION file and the gsutil.spec files to reflect the | |
37 new version number. | |
38 | |
39 Legacy mode and enterprise mode are both embodied in the same gsutil | |
40 archive file, the only difference being that the latter entails running | |
41 one additional command after unpacking the gsutil archive file. So the | |
42 same archive file we've always distributed for gsutil will be used for | |
43 both legacy and enterprise installation modes. | |
44 | |
45 For rpm mode, there's a new tool call pkg_gen.sh, which when run with no | |
46 arguments creates an rpm file at this location: | |
47 | |
48 $HOME/rpmbuild/RPMS/noarch/gsutil-2.0-1.noarch.rpm | |
49 | |
OLD | NEW |