Linux Package Management (Distribute Your App)

(Difference between revisions)
Jump to: navigation, search
(added video and diagram to directions; added to pre-req's from my experience in having to hack through ./configure and make)
(moved pre-req extended to comments section)
Line 10: Line 10:
 
* Getting around the linux file system, sudo'ing, editing files, etc.
 
* Getting around the linux file system, sudo'ing, editing files, etc.
 
* Making and compiling Linux software code
 
* Making and compiling Linux software code
** For example, the commands configure, make, and make install
+
** see extended note in Comments section below
** If students have not compiled in the past, it is common to not have all of the required libraries and modules already installed for the compilation process to succeed. This setup takes time to troubleshoot and setup, and it could be different on each system if students are not using identical operating systems.
+
 
|-
 
|-
 
|'''Learning Objectives''' || Upon completion, students should be able to:
 
|'''Learning Objectives''' || Upon completion, students should be able to:
Line 109: Line 108:
 
=== Comments: ===
 
=== Comments: ===
 
What should the instructor know before using this activity?
 
What should the instructor know before using this activity?
 +
 +
* Students should know how to compile Linux software code before doing this activity.
 +
** There exists an activity which covers this: [[Introduction_to_building_open_source_software]]
 +
** Particularly, students should have experience using the ''configure'', ''make'', and ''make install'' commands
 +
** If students have not compiled in the past, it is common to not have all of the required libraries and modules already installed for the compilation process to succeed. This is a major part of creating RPM's. This setup takes time to troubleshoot and setup, and it could be different on each system if students are not using identical operating systems.
  
 
What are some likely difficulties that an instructor may encounter using this activity?
 
What are some likely difficulties that an instructor may encounter using this activity?
Line 146: Line 150:
  
 
[[Category: Learning_Activity]]
 
[[Category: Learning_Activity]]
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]
+
[[Category: Coding_and_Style]]
 +
[[Category: Product_Packaging_and_Distribution]]
 +
[[Category: Use_and_Evaluate]]

Revision as of 20:04, 12 February 2016

Title Linux package management (distribute desktop apps) (build your own linux package)
Overview Students will learn about rpm and dnf/yum package tooling and then actually create their own package from code, upload it to a public package repository and finally have a classmate install their compiled package. This can be advertised to students as being able to distribute their own linux-based application to the world.
Prerequisite Knowledge Students should be familiar with:
  • Beginner Shell knowledge (linux command line)
  • Getting around the linux file system, sudo'ing, editing files, etc.
  • Making and compiling Linux software code
    • see extended note in Comments section below
Learning Objectives Upon completion, students should be able to:
  • Install RPM's and use the dnf/yum command to inspect and install packages
  • Make and Compile existing code into a binary RPM package
  • Upload a package to an online repository
  • Install a package from an online repository

Background:

  • Are there other related activities?
    • Students can follow the Linux_Beginner_Activity to get command-line basics.
      • Note that the requirements above ask for slightly more in-depth command-line experience via sudo and code compilation.
    • If students need virtual linux machines for command-line access, they can use Virtualbox as seen in this activity.
  • What is the rationale for this activity?
    • Students may wonder how they can distribute linux-based code that they develop out to other everyday users. Not many users enjoy compiling code, so the RPM package structure allows easy installation of binary pre-compiled code packages. Basically, a student could have coded a small sample command-line application and now they can send it to others easily. The other side of it is that students, as users of Linux, will be interfacing with RPM packages not of their making and it will be good to have an understanding of the backends of how this works. Students will interface with the dnf and yum commands even if simply using linux for fun. Now, they can have knowledge into how it works and how they can employ it for their careers and personal uses.


Directions:

  1. Learn about dnf/yum and rpm files. Have students find it themselves. https://en.m.wikipedia.org/wiki/DNF_(software),
  2. Learn about creating rpm's and rpmbuild command
    • RPM Build Example Video - Watch, at least, the first 8 mins of this video from a recording of a local Linux User Group meeting
    • RPM process Diagram from video - Find the diagram that the video references on the page labeled 12-17
      • Document authored by Guru Labs, L.C. released under the CC-BY-NC-ND 2.0 license
  3. Use an existing, easy, mature, yet small project like wget or top (or something that doesn't come standard on most systems) to have students compile and make and package.
  4. Have students rename it so the command line can be run as a test
  5. Have students host the package on a web source (ftp? Some free internet service that makes the .rpm accessible by URL)
  6. Have each student in the class pair up and try to install the other person's RPM and run the new command



Deliverables:

What will the student hand in?


Assessment:

How will the activity be graded?

How will learning will be measured?

Criteria Level 1 (fail) Level 2 (pass) Level 3 (good) Level 4 (exceptional)
Installs and inspects RPMs with dnf/yum
Compiles code into binary RPM
Uploads RPM to COPR or other online repo
Installs colleagues RPM from COPR

Comments:

What should the instructor know before using this activity?

  • Students should know how to compile Linux software code before doing this activity.
    • There exists an activity which covers this: Introduction_to_building_open_source_software
    • Particularly, students should have experience using the configure, make, and make install commands
    • If students have not compiled in the past, it is common to not have all of the required libraries and modules already installed for the compilation process to succeed. This is a major part of creating RPM's. This setup takes time to troubleshoot and setup, and it could be different on each system if students are not using identical operating systems.

What are some likely difficulties that an instructor may encounter using this activity?


Additional Information:

ACM Knowledge Area/Knowledge Unit What ACM Computing Curricula 2013 knowledge area and units does this activity cover? ACM_Body_of_Knowledge
ACM Topic What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf
Level of Difficulty Is this activity easy, medium or challenging?
Estimated Time to Completion How long should it take for the student to complete the activity?
Materials/Environment
  • Access to the shell of a Linux operating system that uses RPM (virtualized or on hardware can work)
  • root access is likely needed - another good vote for virtualized systems (might use openshift or virtualbox)
Author Who wrote this activity?
Source Is there another activity on which this activity is based? If so, please provide a link to the original resource.
License Under which license is this material made available? (http://creativecommons.org/licenses/)

Suggestions for Open Source Community:

Suggestions for an open source community member who is working in conjunction with the instructor.



This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

CC license.png

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox