1,885
edits
Changes
Created page with 'Category:DPI908/SBR600 Labs = Purpose = To learn how to create a repository. = Background Resources = Signing and Creating a Repository for RPM Packages = Required Re…'
[[Category:DPI908/SBR600 Labs]]
= Purpose =
To learn how to create a repository.
= Background Resources =
[[Signing and Creating a Repository for RPM Packages]]
= Required Resources =
Before starting this lab, you will need:
# The RPMs from the [[DPI908/SBR600 RPM Signing Lab|previous lab]].
# An account on a system that can serve files to the web (http or ftp).
= Preparation =
* Check that you have the <code>createrepo</code> package installed.
= Steps =
== Creating the Repository ==
# Place the signed RPMs in a directory on your Fedora system.
# Run this command: <code>createrepo .</code>
# Make a note of the subdirectory and file created by the previous step.
# Make the files available via the web (copy to the appropriate system and directory).
== Creating the Repo and Key Files ==
# Create the repo and key files as outlined on the [[Signing and Creating a Repository for RPM Packages]] page.
# Test that they work as expected.
== Create a Release File ==
# A release package makes it easy for people to get software from your repository. Create a release package as outlined
[[Signing and Creating a Repository for RPM Packages]] page.
{{Admon/tip|Hint: Reusing Packages|The easiest way to create a release package is to take and modify an existing release package. Get the source RPM for the RPM Fusion release package, install it, and edit it to meet your needs. Remember: when working with open source, don't re-invent the wheel unnecessarily!}}
= Deliverable =
Create a blog post describing your experience. Include:
* Notes on what you did, and what worked and didn't work.
* The results, including a link to your release package.
* Your reflections on the tools, process, and experience.
= Purpose =
To learn how to create a repository.
= Background Resources =
[[Signing and Creating a Repository for RPM Packages]]
= Required Resources =
Before starting this lab, you will need:
# The RPMs from the [[DPI908/SBR600 RPM Signing Lab|previous lab]].
# An account on a system that can serve files to the web (http or ftp).
= Preparation =
* Check that you have the <code>createrepo</code> package installed.
= Steps =
== Creating the Repository ==
# Place the signed RPMs in a directory on your Fedora system.
# Run this command: <code>createrepo .</code>
# Make a note of the subdirectory and file created by the previous step.
# Make the files available via the web (copy to the appropriate system and directory).
== Creating the Repo and Key Files ==
# Create the repo and key files as outlined on the [[Signing and Creating a Repository for RPM Packages]] page.
# Test that they work as expected.
== Create a Release File ==
# A release package makes it easy for people to get software from your repository. Create a release package as outlined
[[Signing and Creating a Repository for RPM Packages]] page.
{{Admon/tip|Hint: Reusing Packages|The easiest way to create a release package is to take and modify an existing release package. Get the source RPM for the RPM Fusion release package, install it, and edit it to meet your needs. Remember: when working with open source, don't re-invent the wheel unnecessarily!}}
= Deliverable =
Create a blog post describing your experience. Include:
* Notes on what you did, and what worked and didn't work.
* The results, including a link to your release package.
* Your reflections on the tools, process, and experience.
