/usr/share/doc/ubuntu-packaging-guide-html-pt-br/udd-working.html is in ubuntu-packaging-guide-html-pt-br 0.3.5.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>5. Trabalhando em um pacote — Ubuntu Packaging Guide</title>
<link rel="shortcut icon" href="./_static/images/favicon.ico" type="image/x-icon" />
<link rel="stylesheet" href="./_static/reset.css" type="text/css" />
<link rel="stylesheet" href="./_static/960.css" type="text/css" />
<link rel="stylesheet" href="./_static/base.css" type="text/css" />
<link rel="stylesheet" href="./_static/home.css" type="text/css" />
<link rel="stylesheet" href="./_static/pygments.css" type="text/css" />
<link rel="stylesheet" href="./_static/guide.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '0.3.5',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="./_static/jquery.js"></script>
<script type="text/javascript" src="./_static/underscore.js"></script>
<script type="text/javascript" src="./_static/doctools.js"></script>
<script type="text/javascript" src="./_static/translations.js"></script>
<script type="text/javascript" src="./_static/main.js"></script>
<link rel="top" title="Ubuntu Packaging Guide" href="./index.html" />
<link rel="next" title="6. Buscando revisão e orientação" href="udd-sponsorship.html" />
<link rel="prev" title="4. Obtendo o fonte" href="udd-getting-the-source.html" />
</head>
<body class="home">
<a name="top"></a>
<div class="header-navigation">
<div>
<nav role="navigation">
<ul>
<li class="page_item current_page_item"><a title="Conteúdo" href="index.html">Conteúdo</a>
<li>
<form id="form-search" method="get" action="search.html">
<fieldset>
<input id="input-search" type="text" name="q" value="Search" />
</fieldset>
</form>
</li>
</ul>
</nav>
<a class="logo-ubuntu" href="http://packaging.ubuntu.com/">
<img src="./_static/images/logo-ubuntu.png" width="119" height="27" alt="Ubuntu logo" />
</a>
<a href="http://packaging.ubuntu.com/"><h2>Packaging Guide</h2></a>
</div>
</div>
<div class="header-content">
<div class="clearfix">
<div class="header-navigation-secondary">
<div>
<nav role="navigation">
<ul class="clearfix">
<li class="page_item"><a style="margin-right: 10px"
href="udd-sponsorship.html" title="6. Buscando revisão e orientação"
accesskey="N">próximo</a></li>
<li class="page_item"><a
href="udd-getting-the-source.html" title="4. Obtendo o fonte"
accesskey="P">anterior</a></li>
<li class="page_item"><a class="sub-nav-item" href="index.html">Ubuntu Packaging Guide »</a></li>
</ul>
</nav>
</div>
</div>
</div>
</div>
<div id="content" class="body container_12">
<div class="grid_12">
<!--<section id="main-section">-->
<div class="grid_9 alpha">
<div class="section" id="working-on-a-package">
<h1>5. Trabalhando em um pacote<a class="headerlink" href="#working-on-a-package" title="Link permanente para este título">¶</a></h1>
<p>Uma vez que você tenha a ramificação do pacote fonte em um repositório compartilhado, você deverá criar ramificações adicionais para as correções ou outro trabalho que planeje fazer. Você deverá basear a sua ramificação fora do ramo de origem do pacote para a versão de distribuição para a qual planeja enviar. Normalmente, é a versão de desenvolvimento atual, mas pode ser de versões mais antigas, se você está fazendo um backport de uma SRU, por exemplo.</p>
<div class="section" id="branching-for-a-change">
<h2>5.1. Ramificação para uma alteração<a class="headerlink" href="#branching-for-a-change" title="Link permanente para este título">¶</a></h2>
<p>A primeira coisa a fazer é ter certeza de que seu ramo do pacote fonte está atualizado. Ele estará se você tiver conferido, caso contrário, faça isto:</p>
<div class="highlight-python"><div class="highlight"><pre>$ cd tomboy.dev
$ bzr pull
</pre></div>
</div>
<p>Any updates to the package that have uploaded since your checkout will now be
pulled in. You do not want to make changes to this branch. Instead, create a
branch that will contain just the changes you’re going to make. Let’s say you
want to fix bug 12345 for the Tomboy project. When you’re in the shared
repository you previously created for Tomboy, you can create your bug fix
branch like this:</p>
<div class="highlight-python"><div class="highlight"><pre>$ bzr branch tomboy.dev bug-12345
$ cd bug-12345
</pre></div>
</div>
<p>Now you can do all my work in the <tt class="docutils literal"><span class="pre">bug-12345</span></tt> directory. You make changes
there as necessary, committing as you go along. This is just like doing any
kind of software development with Bazaar. You can make intermediate commits
as often as you like, and when your changes are finished, you will use the
standard <tt class="docutils literal"><span class="pre">dch</span></tt> command (from the <tt class="docutils literal"><span class="pre">devscripts</span></tt> package):</p>
<div class="highlight-python"><div class="highlight"><pre>$ dch -i
</pre></div>
</div>
<p>Isso irá deixá-lo em um editor para adicionar uma entrada ao o arquivo <cite>debian/changelog</cite>.</p>
<p id="link-via-changelog">When you added your <tt class="docutils literal"><span class="pre">debian/changelog</span></tt> entry, you should have included a bug
fix tag that indicated which Launchpad bug issue you’re fixing. The format of
this textual tag is pretty strict: <tt class="docutils literal"><span class="pre">LP:</span> <span class="pre">#12345</span></tt>. The space between the
<tt class="docutils literal"><span class="pre">:</span></tt> and the <tt class="docutils literal"><span class="pre">#</span></tt> is required and of course you should use the actual bug
number that you’re fixing. Your <tt class="docutils literal"><span class="pre">debian/changelog</span></tt> entry might look something
like:</p>
<div class="highlight-python"><div class="highlight"><pre>tomboy (1.12.0-1ubuntu3) trusty; urgency=low
* Don't fubar the frobnicator. (LP: #12345)
-- Bob Dobbs <subgenius@example.com> Mon, 10 Sep 2013 16:10:01 -0500
</pre></div>
</div>
<p>Submeter com o normal:</p>
<div class="highlight-python"><div class="highlight"><pre>bzr commit
</pre></div>
</div>
<p>A hook in bzr-builddeb will use the debian/changelog text as the commit
message and set the tag to mark bug #12345 as fixed.</p>
<p>Isto funciona somente com o bzr-builddeb 2.7.5 e o bzr 2.4, para versões mais antigas, use “debcommit”.</p>
</div>
<div class="section" id="building-the-package">
<h2>5.2. Construindo o pacote<a class="headerlink" href="#building-the-package" title="Link permanente para este título">¶</a></h2>
<p>Along the way, you’ll want to build your branch so that you can test it to
make sure it does actually fix the bug.</p>
<p>A fim de construir o pacote você pode usar o comando <tt class="docutils literal"><span class="pre">bzr</span> <span class="pre">builddeb</span></tt> do pacote <tt class="docutils literal"><span class="pre">bzr-builddeb</span></tt>. Você pode construir um pacote fonte com:</p>
<div class="highlight-python"><div class="highlight"><pre>$ bzr builddeb -S
</pre></div>
</div>
<p>(<tt class="docutils literal"><span class="pre">bd</span></tt> é um nome alternativo para o <tt class="docutils literal"><span class="pre">builddeb</span></tt>.) Você pode deixar o pacote não assinado, anexando <tt class="docutils literal"><span class="pre">--</span> <span class="pre">-uc</span> <span class="pre">-us`</span></tt> para o comando.</p>
<p>Também é possível utilizar as suas ferramentas normais, contanto que elas sejam capazes de remover os diretórios .bzr do pacote, por exemplo:</p>
<div class="highlight-python"><div class="highlight"><pre>$ debuild -i -I
</pre></div>
</div>
<p>If you ever see an error related to trying to build a native package without a
tarball, check to see if there is a <tt class="docutils literal"><span class="pre">.bzr-builddeb/default.conf</span></tt> file
erroneously specifying the package as native. If the changelog version has a
dash in it, then it’s not a native package, so remove the configuration file.
Note that while <tt class="docutils literal"><span class="pre">bzr</span> <span class="pre">builddeb</span></tt> has a <tt class="docutils literal"><span class="pre">--native</span></tt> switch, it does not have a
<tt class="docutils literal"><span class="pre">--no-native</span></tt> switch.</p>
<p>Uma vez que você tenha obtido o pacote fonte, você pode construí-lo normalmente com “pbuilder-dist”` (ou “pbuilder” ou “sbuild”_).</p>
</div>
</div>
<div class="divide"></div>
</div>
<div id="sidebar" class="grid_3 omega">
<div class="container-tweet">
<h3>Tabela de Conteúdo</h3>
<div class="toc">
<ul>
<li><a class="reference internal" href="#">5. Trabalhando em um pacote</a><ul>
<li><a class="reference internal" href="#branching-for-a-change">5.1. Ramificação para uma alteração</a></li>
<li><a class="reference internal" href="#building-the-package">5.2. Construindo o pacote</a></li>
</ul>
</li>
</ul>
</div>
<div class="browse-guide">
<h3>Browse The Guide:</h3>
<ul>
<li class="prev">
<a href="udd-getting-the-source.html"
title="Tópico anterior: 4. Obtendo o fonte">Go Previous</a>
</li>
<li class="center">
<a title="Back to Index" href="index.html">Index Guide</a>
</li>
<li class="next">
<a href="udd-sponsorship.html"
title="Próximo tópico: 6. Buscando revisão e orientação">Go Next</a>
</li>
</ul>
<span>Esta Página:</span> <a href="./_sources/udd-working.txt"
rel="nofollow">Exibir Fonte</a>
</div>
</div>
<div id="back_top"><a href="#top">Back to Top</a></div>
</div>
<!--</section>-->
</div>
</div>
<div class="shadow"></div>
<footer>
<div>
Version: 0.3.5.
<a href="https://bugs.launchpad.net/ubuntu-packaging-guide">Report bugs</a> or
<a href="https://code.launchpad.net/~ubuntu-packaging-guide-team/ubuntu-packaging-guide/trunk">grab the source code</a> from Launchpad.
Criado usando <a href="http://sphinx-doc.org/">Sphinx</a> 1.2.2.
<br />
© Copyright 2010-2014 , Ubuntu Developers, Creative Commons Attribution-ShareAlike 3.0.
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">
Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">
<img alt="Creative Commons License" style="border-width:0"
src="./_static/images/cc-by-sa.png" /></a>
<br />
<a href="http://people.ubuntu.com/~mitya57/ubuntu-packaging-guide-readme.html#translating">Help translate</a> or
<a href="./_static/translators.html">view the list of translators</a>.
</div>
</footer>
</body>
</html>
|