Difference between revisions of "Clean Up the Pidora Kickstart File"
(→Project News) |
(→Goals by Release) |
||
| Line 43: | Line 43: | ||
Goals for each release and plans for reaching those goals: | Goals for each release and plans for reaching those goals: | ||
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | <!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | ||
| − | * 0.1 - Identify package dependencies listed in the recent version of a kickstart file and remove unnecessary packages from | + | * 0.1 - Create a sub-file to separate configurations and a list of packages. Identify package dependencies listed in the recent version of a kickstart file and remove unnecessary packages from the kickstart file. |
| − | * 0.2 - Remove/add package dependencies in a pkg.list sub file | + | * 0.2 - Remove/add package dependencies in a pkg.list sub file based on other packages' update. Create/update a automation script, which will allows me to easily tell packages. |
* 0.3 - Finalize a kickstart file and sub-file. | * 0.3 - Finalize a kickstart file and sub-file. | ||
Revision as of 13:21, 23 November 2013
Contents
Clean Up the Pidora Kickstart File
As of Nov. 18 / 2013, this page has been updated for the project description, its details, and project news.
Project Description
The kickstart file allows Pidora to be installed with the pre-setup configuration, unattended. The goal of this project is to prevent the unnecessary packages from being installed, which contributes the small storage maximization.
Project Leader
Yonghoon Shin
Project Contributor(s)
Project Details
Assignment
- Minimize the number of packages and create the kickstart-dependent sub-file by an automatic bash script which is to be created by me.
Project Plan
Tracking
Key contacts
Andrew Greene
Goals by Release
Goals for each release and plans for reaching those goals:
- 0.1 - Create a sub-file to separate configurations and a list of packages. Identify package dependencies listed in the recent version of a kickstart file and remove unnecessary packages from the kickstart file.
- 0.2 - Remove/add package dependencies in a pkg.list sub file based on other packages' update. Create/update a automation script, which will allows me to easily tell packages.
- 0.3 - Finalize a kickstart file and sub-file.
Communication
Mailing Lists
Upsteam Wiki and Web
Links/Bugs/Tracking
Source Code Control
Blogs
Non-Seneca Participants
Planets
Project News
Oct. 9th / 2013 - Start!
Nov. 8th / 2013 - A package list has been separated as a file named pkg.ks.
Nov. 15th / 2013 - An updated gg script to find package dependencies has been created and updated.
Nov. 18th / 2013 - Important dependencies and unnecessary packages have been chosen. A pidora image file will be released soon
Nov. 23rd / 2013 - An official release 0.1 has been released. The official release 0.1 package contains a cleaned Kickstart file, a package list ks file, and scripts.
