|
|
31.
|
|
|
Getting Help
|
|
|
|
|
Getting Help
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:133(title)
|
|
|
32.
|
|
|
If you need assistance on these steps, or if you have questions about REVU, you can ask in #ubuntu-motu on the Freenode IRC network.
|
|
|
|
|
If you need assistance on these steps, or if you have questions about REVU, you can ask in #ubuntu-motu on the Freenode IRC network.
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:134(para)
|
|
|
33.
|
|
|
Merges and Syncs
|
|
|
|
|
Merges and Syncs
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:143(title)
|
|
|
34.
|
|
|
<emphasis role="bold">Requirements:</emphasis> build-essential, automake, gnupg, lintian, fakeroot, patchutils, debhelper and <xref linkend="gs-pbuilder"/>.
|
|
|
|
|
<emphasis role="bold">Requirements:</emphasis> build-essential, automake, gnupg, lintian, fakeroot, patchutils, debhelper and <xref linkend="gs-pbuilder"/>.
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:147(para)
|
|
|
35.
|
|
|
<phrase>Ubuntu</phrase> is based on the Debian Linux distribution and uses the same package management system (APT). At the beginning of each <phrase>Ubuntu</phrase> development cycle, the packages in <phrase>Ubuntu</phrase> are updated to those in the Debian unstable branch. However, because <phrase>Ubuntu</phrase> is not the same as Debian, some of the packages need to be modified to work in <phrase>Ubuntu</phrase>. There might also be bug fixes that <phrase>Ubuntu</phrase> developers have introduced into the packages. You can determine whether this has taken place by noting the package version. If the package version includes ubuntu in it (an example would be gimp-2.2.9-3ubuntu2), then the <phrase>Ubuntu</phrase> developers have made changes, and it is no longer the same as the Debian package. There are more than 1000 such modified packages in the Universe repository.
|
|
|
|
|
<phrase>Ubuntu</phrase> is based on the Debian Linux distribution and uses the same package management system (APT). At the beginning of each <phrase>Ubuntu</phrase> development cycle, the packages in <phrase>Ubuntu</phrase> are updated to those in the Debian unstable branch. However, because <phrase>Ubuntu</phrase> is not the same as Debian, some of the packages need to be modified to work in <phrase>Ubuntu</phrase>. There might also be bug fixes that <phrase>Ubuntu</phrase> developers have introduced into the packages. You can determine whether this has taken place by noting the package version. If the package version includes ubuntu in it (an example would be gimp-2.2.9-3ubuntu2), then the <phrase>Ubuntu</phrase> developers have made changes, and it is no longer the same as the Debian package. There are more than 1000 such modified packages in the Universe repository.
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:152(para)
|
|
|
36.
|
|
|
At the start of each Ubuntu development cycle, a decision is made regarding these Ubuntu versioned packages. Of course if the Debian version hasn't changed since the last <phrase>Ubuntu</phrase> release, then nothing needs to be changed. However, if there is a newer version of the package in Debian, then one of two things should happen. If all of the reasons for Ubuntu modifications (bug fixes, dependencies, etc.) are fixed in the new Debian package, then we can just take the Debian package directly. This decision is called a <emphasis>sync</emphasis>. However, if the new Debian version has the same issues that caused the Ubuntu version to be made, then those changes need to be applied to the new Debian version, too. This decision is called <emphasis>merging</emphasis>.
|
|
|
|
|
At the start of each Ubuntu development cycle, a decision is made regarding these Ubuntu versioned packages. Of course if the Debian version hasn't changed since the last <phrase>Ubuntu</phrase> release, then nothing needs to be changed. However, if there is a newer version of the package in Debian, then one of two things should happen. If all of the reasons for Ubuntu modifications (bug fixes, dependencies, etc.) are fixed in the new Debian package, then we can just take the Debian package directly. This decision is called a <emphasis>sync</emphasis>. However, if the new Debian version has the same issues that caused the Ubuntu version to be made, then those changes need to be applied to the new Debian version, too. This decision is called <emphasis>merging</emphasis>.
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:163(para)
|
|
|
37.
|
|
|
Merging Tutorial
|
|
|
|
|
Merging Tutorial
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:175(title)
|
|
|
38.
|
|
|
The merging process involves looking at the changes to both the Debian and Ubuntu source packages and determining what has changed and which changes are Ubuntu-specific. Let us now look at an example, a popular CD creation program called <application>xcdroast</application>.
|
|
|
|
|
The merging process involves looking at the changes to both the Debian and Ubuntu source packages and determining what has changed and which changes are Ubuntu-specific. Let us now look at an example, a popular CD creation program called <application>xcdroast</application>.
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:176(para)
|
|
|
39.
|
|
|
To start, make a folder to hold our project, then navigate there:
|
|
|
|
|
To start, make a folder to hold our project, then navigate there:
|
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:181(para)
|
|
|
40.
|
|
|
mkdir ~/xcdroast
cd ~/xcdroast |
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
mkdir ~/xcdroast
cd ~/xcdroast |
|
Translated and reviewed by
Malcolm Parsons
|
|
|
|
Located in
C/ubuntu.xml:182(screen)
|
