|
|
274.
|
|
|
Every effort has been made to ensure that the information compiled in this publication is accurate and correct. However, this does not guarantee complete accuracy. Neither Canonical Ltd., the authors, nor translators shall be held liable for possible errors or the consequences thereof.
|
|
|
|
|
我们已尽可能确保本文档所编写信息的准确性和正确性，不过即便如此，仍无法保证其完全正确。因此对其中可能存在的错误或由此造成的后果，Canonical Ltd. 作者和译者恕不负责。
|
|
Translated and reviewed by
stone_unix
|
|
|
|
Located in
C/bookinfo.xml:4(para)
|
|
|
275.
|
|
|
Some of the software and hardware descriptions cited in this publication may be registered trademarks and may thus fall under copyright restrictions and trade protection laws. In no way do the authors make claim to any such names.
|
|
|
|
|
在此公布的一些软硬件描述中引用的可能被注册为商标，并可能因此受限于版权和贸易保护法。作者不会以任何方式来诉求这些名称的所有权。
|
|
Translated and reviewed by
stone_unix
|
|
|
|
Located in
C/bookinfo.xml:8(para)
|
|
|
276.
|
|
|
THIS DOCUMENTATION IS PROVIDED BY THE AUTHORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/bookinfo.xml:9(para)
|
|
|
277.
|
|
|
The Ubuntu Documentation Project
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/bookinfo.xml:3(publishername)
|
|
|
278.
|
|
|
Basic Packaging
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/basic.xml:15(title)
|
|
|
279.
|
|
|
Two of the problems that many novice packagers face are that there are multiple ways of packaging, and there is more than one tool to do the job. We will go through three examples with the common build systems. First, we will use no build helper. This approach is usually the most difficult and is not often used in practice but gives the most straightforward look at the packaging process. Second, we will use <application>debhelper</application>, the most common build system in Debian. It helps the packager by automating repetitive tasks. Third, we will briefly cover the <emphasis role="bold">C</emphasis>ommon <emphasis role="bold">D</emphasis>ebian <emphasis role="bold">B</emphasis>uild <emphasis role="bold">S</emphasis>ystem (<application>CDBS</application>), a more streamlined build system that uses <application>debhelper</application>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/basic.xml:17(para)
|
|
|
280.
|
|
|
Package development often requires installing many packages (especially <application>-dev</application> packages containing headers and other common development files) that are not part of a normal desktop <phrase>Ubuntu</phrase> installation. If you want to avoid installing extra packages or would like to develop for a different <phrase>Ubuntu</phrase> release (the development one, for instance) from what you currently have, the use of a chroot environment is highly recommended. A guide to setting up a <xref linkend="appendix-chroot"/> can be found in the Appendix.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/basic.xml:33(para)
|
|
|
281.
|
|
|
Packaging From Scratch
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/basic.xml:46(title)
|
|
|
282.
|
|
|
<emphasis role="bold">Requirements:</emphasis> build-essential, automake, gnupg, lintian, fakeroot and <xref linkend="gs-pbuilder"/>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/basic.xml:48(para)
|
|
|
283.
|
|
|
In this example we will be using the GNU <application><ulink url="http://www.gnu.org/software/hello/hello.html">hello</ulink></application> program as our example. You can download the source tarball from <ulink url="http://ftp.gnu.org/gnu/hello/hello-2.1.1.tar.gz">ftp.gnu.org</ulink>. For the purposes of this example, we will be using the <filename>~/hello/</filename> directory.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/basic.xml:52(para)
|
