[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[debian-devel:11481] Re: Separate tarball/patch build system (Re: Re: Bug#JP/1134: mnews-1.22 licence problem)
At Wed, 26 Jan 2000 08:08:47 +0900,
Atsuhito Kohda <kohda@xxxxxxxxxxxxxxxxxxxx> wrote:
> > orig.tar.gzが originalと違ってしまうのは好きではないので
>
> これが共通認識になってるならどっかに書いておく方が良い
> と思うのですが、既にどっかに書いてますか？
うーむ はっきり書いてあるのはないのかも?
ただ
dpkg (1.4.0.13) experimental; urgency=low
* Patch from Guy Maor <maor@xxxxxxxxxxxxxx> to dpkg-source.pl to support
pristine (MD5-equivalent) upstream sources.
あたりから、そうした方がよいだろうという認識はあったような。
あとはあまり orig.tar.gz に関して言及されてませんねぇ。
Debian Policy Manual だと
2.4.3. Changes to the upstream sources
--------------------------------------
If changes to the source code are made that are generally applicable
please try to get them included in the upstream version of the package
by supplying the upstream authors with the changes in whatever form
they prefer.
If you need to configure the package differently for Debian or for
Linux, and the upstream source doesn't provide a way to configure it
the way you need to, please add such configuration facilities (for
example, a new `autoconf' test or `#define') and send the patch to the
upstream authors, with the default set to the way they originally had
it. You can then easily override the default in your `debian/rules'
or wherever is appropriate.
Please make sure that the `configure' utility detects the correct
architecture specification string (refer to Section 5.1, `Architecture
specification strings' for details).
If you need to edit a `Makefile' where GNU-style `configure' scripts
are used, you should edit the `.in' files rather than editing the
`Makefile' directly. This allows the user to reconfigure the package
if necessary. You should _not_ configure the package and edit the
generated `Makefile'! This makes it impossible for someone else to
later reconfigure the package.
だし、Developers Reference だと
5.5. Packages
-------------
There are two types of Debian packages, namely _source_ and _binary_
packages.
Source packages consist of either two or three files: a `.dsc' file,
and either a `.tar.gz' file or both an `.orig.tar.gz' and a `.diff.gz'
file.
If a package is developed specially for Debian and is not distributed
outside of Debian, there is just one `.tar.gz' file which contains the
sources of the program. If a package is distributed elsewhere too, the
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
`.orig.tar.gz' file stores the so-called _upstream source code_, that
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is the source code that's distributed from the _upstream maintainer_
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(often the author of the software). In this case, the `.diff.gz'
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
contains the changes made by the Debian maintainer.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The `.dsc' lists all the files in the source package together with
checksums (`md5sums') and some additional info about the package
(maintainer, version, etc.).
くらいかなぁ
> ちょっと古い話になりますが、私がパッケージ作り始めた
> 頃に「Debina GNU/Linux に関する Q&A」の topics-ml-428.html
> にある
かなーり古いドキュメントなので消した方がいいですね…
PS.
なんか Packaging Manual によると debian/rules に
`get-orig-source' (optional)
This target fetches the most recent version of the original
source package from a canonical archive site (via FTP or WWW, for
example), does any necessary rearrangement to turn it into the
original source tarfile format described below, and leaves it in
the current directory.
This target may be invoked in any directory, and should take care
to clean up any temporary files it may have left.
This target is optional, but providing it if possible is a good
idea.
というのもあるのですね
--
鵜飼文敏