1,885
edits
Changes
no edit summary
* Take the software you compiled last week and package it (not Nled!). Blog about the experience. Include a link to your source RPM (and optionally your binary RPM) from your blog.
= Week 4 (February 2) - Working with Open Source Communities and Project Release 0.0 =
* Free Software and Open Source
# Test it with mock
= Week 5 (February 9) - Basic Build I == Week 6 (February 16) - Basic Build II =
* We analyzed the [[Winter 2009 SBR 600 Fedora Mass Rebuild|mass rebuild]] results so far to find the slowest 15 packages: [[Winter 2009 SBR600 Packages of Interest]]
* Prepare one of the CDOT machines for a non-mock build of a slow package. See [[Winter_2009_SBR600_Packages_of_Interest#Preparing_to_test_distcc|Preparing to test distcc]]
= Week 7 (February 23) - Basic Build III - Project Release 0.1 =
= Study Week (March 2) =
= Week 8 (March 9) - Server Farms & Distributed Processing I =
Machine codes:
* Blog an analysis of the /var/f10source/buildall.log file on Scotland.
= Week 9 (March 16) - Server Farms & Distributed Processing II =
== Signing RPM packages ==
# Blog about this lab, and include a link to your repository RPM package.
= Week 10 (March 23) - Server Farms & Distributed Processing III - Project Release 0.2 == Week 11 (March 30) - Supporting Technologies I == Week 12 (April 6) = == Using git ===== Resources ===* git web site: http://git- Supporting Technologies II scm.com/* git tutorial: <code>man gittutorial</code> or http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html* git documentation: http://git-scm.com/documentation* Fedora packages: <code>git, gitk</code> === Lab Steps ===# Select a CDOT system that no one else is using.# Make a backup archive of the /etc directory: <code>tar cvzf ~/etc-backup.tgz /etc</code># Put the <code>/etc</code> directory under git control and do an initial commit.# Experiment with making changes in /etc and committing those changes.# Create an experimental branch and checkout that branch.# Make radical changes in /etc. Experiment with switching back and forth between the master and experimental branches.# When you're done, checkout the master branch and delete the experimental branch. ''ToDo'''* Blog about your using git -- what commands you used, what worked well, what was confusing, what you like/don't like. = Week 13 (April 13) - Project Release 0.3 & Presentations =
= Exam Week (April 20) =
