On 05/04/14 at 11:31am, Dave Young wrote:
On 05/04/14 at 10:39am, Arthur Zou wrote:
> Currently this work is done by firstboot. Now we move to anaconda addon
> to configurate in the system installation process.
>
> Signed-off-by: Arthur Zou <zzou(a)redhat.com>
> ---
> addon-Makefile | 82 ++++++++++++
> addon-README | 32 +++++
> addon-__init__.py | 0
> addon-common.py | 88 ++++++++++++
> addon-constants.py | 23 ++++
> addon-gui-__init__.py | 0
> addon-gui-spokes-__init__.py | 0
> addon-gui-spokes-fedora.glade | 218 ++++++++++++++++++++++++++++++
> addon-gui-spokes-kdump.glade | 274 ++++++++++++++++++++++++++++++++++++++
> addon-gui-spokes-kdump.py | 192 ++++++++++++++++++++++++++
> addon-i18n.py | 27 ++++
> addon-ks-__init__.py | 0
> addon-ks-kdump.py | 128 ++++++++++++++++++
> addon-po-Makefile | 78 +++++++++++
> addon-po-kdump-anaconda-addon.pot | 81 +++++++++++
> addon-tui-__init__.py | 0
> addon-tui-spokes-__init__.py | 0
> addon-tui-spokes-kdump.py | 87 ++++++++++++
Rethinking about the directory layout for the addon it might be better to
maintain them in a subdirectory instead of the dash seperated flat filename.
One reason is these files could be stable and they will not be modified
frequently. So we can keep them as is like below:
kdump-annaconda-addon\Makefile
kdump-annaconda-addon\gui\__init__.py
kdump-annaconda-addon\gui\spokes\__init__.py
...
For each time we have some changes to the code, we can create a tarball
kdump-annaconda-addon-$(version).tar.gz and upload it to lookaside cache
server. In rpm spece file we also reference the tarball as SOURCE.
For translation files it sounds better that we maintain another tarball
During install phase, we extract the two tarballs and call the toplevel
kdump-annaconda-addon\Makefile
Thanks
Dave