m (Sergiodj moved page FedoraGDBMaintainerGuide to Fedora GDB Maintainer Guide: Use underscore) |
(Adding some sections) |
||
| Line 2: | Line 2: | ||
This is a guide for the Fedora GDB package maintainer. The reason we have a specific document for the package (which builds on top of the existing official Fedora packaging documentation) is because we carry several local patches along with the project's official codebase. | This is a guide for the Fedora GDB package maintainer. The reason we have a specific document for the package (which builds on top of the existing official Fedora packaging documentation) is because we carry several local patches along with the project's official codebase. | ||
== Getting ready == | |||
You will need to install some packages before we start. | |||
<pre> | |||
dnf install fedpkg rpm-build | |||
</pre> | |||
You will also need to configure Kerberos authentication in order to use <code>fedpkg</code>. See [[Infrastructure/Kerberos]] for details. | |||
== Cloning the repository == | |||
The Fedora GDB repository is located at [https://src.fedoraproject.org/rpms/gdb]. You can clone it by doing: | |||
<pre> | |||
fedpkg clone gdb | |||
</pre> | |||
After this, you will see a <code>gdb</code> directory, where you can use <code>git switch</code> to switch to a specific release branch. | |||
If you are like me and prefers to have each branch in its own directory, you can do that using: | |||
<pre> | |||
fedpkg clone --branches gdb | |||
</pre> | |||
You should see several directories named like <code>f28/</code>, <code>f29/</code>, <code>f30/</code>, etc. If you choose this approach, you will have to manually clone every time Fedora branches. For example, supposing that Fedora branches <code>f30</code>, you will have to do: | |||
<pre> | |||
fedpkg clone --branch f30 gdb && mv gdb f30 | |||
</pre> | |||
== Downloading the sources == | |||
Fedora stores the source files (i.e., the tarballs) for the package in a separate cache. This means that when you clone the repository, you will not automatically obtain the tarballs necessary to build the package. In order to do that, you should execute: | |||
<pre> | |||
fedpkg sources | |||
</pre> | |||
Revision as of 14:15, 1 April 2020
Introduction
This is a guide for the Fedora GDB package maintainer. The reason we have a specific document for the package (which builds on top of the existing official Fedora packaging documentation) is because we carry several local patches along with the project's official codebase.
Getting ready
You will need to install some packages before we start.
dnf install fedpkg rpm-build
You will also need to configure Kerberos authentication in order to use fedpkg. See Infrastructure/Kerberos for details.
Cloning the repository
The Fedora GDB repository is located at [1]. You can clone it by doing:
fedpkg clone gdb
After this, you will see a gdb directory, where you can use git switch to switch to a specific release branch.
If you are like me and prefers to have each branch in its own directory, you can do that using:
fedpkg clone --branches gdb
You should see several directories named like f28/, f29/, f30/, etc. If you choose this approach, you will have to manually clone every time Fedora branches. For example, supposing that Fedora branches f30, you will have to do:
fedpkg clone --branch f30 gdb && mv gdb f30
Downloading the sources
Fedora stores the source files (i.e., the tarballs) for the package in a separate cache. This means that when you clone the repository, you will not automatically obtain the tarballs necessary to build the package. In order to do that, you should execute:
fedpkg sources