Difference between revisions of "Automatic ExclusiveArch Addition/Removal"

From CDOT Wiki
Jump to: navigation, search
Line 33: Line 33:
 
Goals for each release and plans for reaching those goals:
 
Goals for each release and plans for reaching those goals:
 
<!-- Note: each contributor is expected to 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 contributor is expected to 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 Have a rough working script (May not include automatic download of packages)
0.1 Have a rough working script (May not include automatic download of packages)
+
* 0.2 Add extra features, get automatic download of packages working, debug
0.2 Add extra features, get automatic download of packages working, debug
+
* 0.3 Write documentation, polish off program
0.3 Write documentation, polish off program
 
'''
 
 
== Communication ==
 
== Communication ==
  

Revision as of 08:23, 3 February 2011

Automatic ExclusiveArch Addition/Removal

Project Description

The purpose of this project is to write a script that will automatically loop through a given list of packages and automatically download them. It will then change a line specified by the user.

Project Leader(s)

Matthew Tuori

Project Contributor(s)

Project Details

Script will be written in Python.Input can include a csv file or command line arguements. There will be a config file.

Project Plan

Tracking mechanism (bugzilla, trac, github, ...): To be determined - Still have to look at the available options to determine the solution that is best for this project.

Key contacts: ctyler PaulW

Goals for each release and plans for reaching those goals:

  • 0.1 Have a rough working script (May not include automatic download of packages)
  • 0.2 Add extra features, get automatic download of packages working, debug
  • 0.3 Write documentation, polish off program

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

http://www.tuori.tk

Seneca Particpants

Non-Seneca Participants

Planets

Project News