# HG changeset patch # User Yoshiki Yazawa # Date 1220344031 -32400 # Node ID ef197f25f11e4d0a8a475b245b70046de7cb7ef6 # Parent b96d7f6504e517b84484acd8f0416287a63b8244 more hgext.tex diff -r b96d7f6504e5 -r ef197f25f11e ja/hgext.tex --- a/ja/hgext.tex Mon Sep 01 18:20:56 2008 +0900 +++ b/ja/hgext.tex Tue Sep 02 17:27:11 2008 +0900 @@ -186,103 +186,174 @@ トワークファイルシステムは考慮されていない． \end{itemize} -The \hgext{inotify} extension is not yet shipped with Mercurial as of -May~2007, so it's a little more involved to set up than other -extensions. But the performance improvement is worth it! +%The \hgext{inotify} extension is not yet shipped with Mercurial as of +%May~2007, so it's a little more involved to set up than other +%extensions. But the performance improvement is worth it! + +2007年5月までは\hgext{inotify}拡張はMercurialに同梱されていなかった．その +ため，セットアップは他の拡張に比べてやや複雑だが，得られる性能向上はには +それだけの価値がある． -The extension currently comes in two parts: a set of patches to the -Mercurial source code, and a library of Python bindings to the -\texttt{inotify} subsystem. +%The extension currently comes in two parts: a set of patches to the +%Mercurial source code, and a library of Python bindings to the +%\texttt{inotify} subsystem. + +現在，拡張は2つのパートに分かれている．Mercurialソースコードへのパッチと +\texttt{inotify}サブシステムへのPythonバインディングライブラリである． + \begin{note} - There are \emph{two} Python \texttt{inotify} binding libraries. One - of them is called \texttt{pyinotify}, and is packaged by some Linux - distributions as \texttt{python-inotify}. This is \emph{not} the - one you'll need, as it is too buggy and inefficient to be practical. +% There are \emph{two} Python \texttt{inotify} binding libraries. One +% of them is called \texttt{pyinotify}, and is packaged by some Linux +% distributions as \texttt{python-inotify}. This is \emph{not} the +% one you'll need, as it is too buggy and inefficient to be practical. + +Pythonの\texttt{inotify}バインディングライブラリは\emph{2つ}ある．1つは +\texttt{pyinotify}であり，いくつかのLinuxディストリビューションでは +\texttt{python-inotify}としてパッケージ化されている．これはバグが非常に多 +く，実用するには非効率的であり，使うべきで\emph{ない}． \end{note} -To get going, it's best to already have a functioning copy of -Mercurial installed. +%To get going, it's best to already have a functioning copy of +%Mercurial installed. +先へ進むに当って，正しく機能するMercurialがインストールされていることが +望ましい． + \begin{note} - If you follow the instructions below, you'll be \emph{replacing} and - overwriting any existing installation of Mercurial that you might - already have, using the latest ``bleeding edge'' Mercurial code. - Don't say you weren't warned! +% If you follow the instructions below, you'll be \emph{replacing} and +% overwriting any existing installation of Mercurial that you might +% already have, using the latest ``bleeding edge'' Mercurial code. +% Don't say you weren't warned! +以下の指示に従ってインストールしたMercurialを，最新のMercurialコードで +\emph{置き換える}ことができる．（警告されなかったとは言わないこと） + \end{note} \begin{enumerate} -\item Clone the Python \texttt{inotify} binding repository. Build and - install it. +%\item Clone the Python \texttt{inotify} binding repository. Build and +% install it. +\item Python \texttt{inotify}バインディングのリポジトリをクローンし，ビ + ルドとインストールを行う． \begin{codesample4} hg clone http://hg.kublai.com/python/inotify cd inotify python setup.py build --force sudo python setup.py install --skip-build \end{codesample4} -\item Clone the \dirname{crew} Mercurial repository. Clone the - \hgext{inotify} patch repository so that Mercurial Queues will be - able to apply patches to your cope of the \dirname{crew} repository. +%\item Clone the \dirname{crew} Mercurial repository. Clone the +% \hgext{inotify} patch repository so that Mercurial Queues will be +% able to apply patches to your cope of the \dirname{crew} repository. + \item Merecurialの\dirname{crew}リポジトリをクローンす + る．\hgext{inotify}パッチリポジトリをクローンし，Mercurial Queues + が\dirname{crew}リポジトリにパッチを当てられるようにする． \begin{codesample4} hg clone http://hg.intevation.org/mercurial/crew hg clone crew inotify hg clone http://hg.kublai.com/mercurial/patches/inotify inotify/.hg/patches \end{codesample4} -\item Make sure that you have the Mercurial Queues extension, - \hgext{mq}, enabled. If you've never used MQ, read - section~\ref{sec:mq:start} to get started quickly. -\item Go into the \dirname{inotify} repo, and apply all of the - \hgext{inotify} patches using the \hgxopt{mq}{qpush}{-a} option to - the \hgxcmd{mq}{qpush} command. +%\item Make sure that you have the Mercurial Queues extension, +% \hgext{mq}, enabled. If you've never used MQ, read +% section~\ref{sec:mq:start} to get started quickly. + +\item Mercurial Queues拡張（\hgext{mq}）が有効になっていることを確認す + る．MQを使ったことがなければ，\ref{sec:mq:start}を一読することをお + すすめする． + +%\item Go into the \dirname{inotify} repo, and apply all of the +% \hgext{inotify} patches using the \hgxopt{mq}{qpush}{-a} option to +% the \hgxcmd{mq}{qpush} command. +\item \dirname{inotify}リポジトリへ行き，\hgxcmd{mq}{qpush}コマンドに + \hgxopt{mq}{qpush}{-a}オプションを使って\hgext{inotify}のパッチをす + べて適用する． + \begin{codesample4} cd inotify hg qpush -a \end{codesample4} - If you get an error message from \hgxcmd{mq}{qpush}, you should not - continue. Instead, ask for help. -\item Build and install the patched version of Mercurial. +% If you get an error message from \hgxcmd{mq}{qpush}, you should not +% continue. Instead, ask for help. + +\hgxcmd{mq}{qpush}でエラーが起きた場合，先へ進まずに助言を求めて欲しい． + +%\item Build and install the patched version of Mercurial. +\item パッチを当てたMercurialをビルドしてインストールする． \begin{codesample4} python setup.py build --force sudo python setup.py install --skip-build \end{codesample4} \end{enumerate} -Once you've build a suitably patched version of Mercurial, all you -need to do to enable the \hgext{inotify} extension is add an entry to -your \hgrc. +%Once you've build a suitably patched version of Mercurial, all you +%need to do to enable the \hgext{inotify} extension is add an entry to +%your \hgrc. + +適切なパッチの当ったMercurialをビルドすれば，後は\hgext{inotify}拡張を利 +用するように\hgrc を設定するだけである． + \begin{codesample2} [extensions] inotify = \end{codesample2} -When the \hgext{inotify} extension is enabled, Mercurial will -automatically and transparently start the status daemon the first time -you run a command that needs status in a repository. It runs one -status daemon per repository. +%When the \hgext{inotify} extension is enabled, Mercurial will +%automatically and transparently start the status daemon the first time +%you run a command that needs status in a repository. It runs one +%status daemon per repository. + +\hgext{inotify}が有効になっていると，Mercurialはリポジトリ内でコマンドが +最初に実行された時に自動的かつ透過的にステータスデーモンを起動する．リポ +ジトリ1つごとに1つのステータスデーモンが起動される． -The status daemon is started silently, and runs in the background. If -you look at a list of running processes after you've enabled the -\hgext{inotify} extension and run a few commands in different -repositories, you'll thus see a few \texttt{hg} processes sitting -around, waiting for updates from the kernel and queries from -Mercurial. +%The status daemon is started silently, and runs in the background. If +%you look at a list of running processes after you've enabled the +%\hgext{inotify} extension and run a few commands in different +%repositories, you'll thus see a few \texttt{hg} processes sitting +%around, waiting for updates from the kernel and queries from +%Mercurial. + +ステータスデーモンは何も出力を行わず，バックグラウンドで動作す +る．\hgext{inotify}拡張を有効にした後で別のリポジトリ内でいくつかコマンド +を実行し，実行中のプロセスのリストを見ると，いくつかの\texttt{hg}プロセス +がカーネルからのアップデートとMercurialからの問い合わせを待っているのが +見られるだろう． -The first time you run a Mercurial command in a repository when you -have the \hgext{inotify} extension enabled, it will run with about the -same performance as a normal Mercurial command. This is because the -status daemon needs to perform a normal status scan so that it has a -baseline against which to apply later updates from the kernel. -However, \emph{every} subsequent command that does any kind of status -check should be noticeably faster on repositories of even fairly -modest size. Better yet, the bigger your repository is, the greater a -performance advantage you'll see. The \hgext{inotify} daemon makes -status operations almost instantaneous on repositories of all sizes! +%The first time you run a Mercurial command in a repository when you +%have the \hgext{inotify} extension enabled, it will run with about the +%same performance as a normal Mercurial command. This is because the +%status daemon needs to perform a normal status scan so that it has a +%baseline against which to apply later updates from the kernel. +%However, \emph{every} subsequent command that does any kind of status +%check should be noticeably faster on repositories of even fairly +%modest size. Better yet, the bigger your repository is, the greater a +%performance advantage you'll see. The \hgext{inotify} daemon makes +%status operations almost instantaneous on repositories of all sizes! + +\hgext{inotify}拡張を有効にし，リポジトリ内でMercurialコマンドを最初に実 +行した時は通常のMercurialコマンドと同様の性能で動く．ステータスデーモンは +通常のステータススキャンを行い，カーネルから更新の通知を受けるためのベー +スラインを取得しておかなければならないからである．一方で，後続のステータ +スチェックを行う\emph{すべての}コマンドは，そこそこの大きさのリポジトリに +対しても目に見えて高速化される．さらにリポジトリが大きくなるに連れて性能 +の向上は大きくなる．\hgext{inotify}デーモンは，リポジトリのサイズに関わら +ず，ステータス取得をほぼ瞬時に行うことができる． -If you like, you can manually start a status daemon using the -\hgxcmd{inotify}{inserve} command. This gives you slightly finer -control over how the daemon ought to run. This command will of course -only be available when the \hgext{inotify} extension is enabled. +%If you like, you can manually start a status daemon using the +%\hgxcmd{inotify}{inserve} command. This gives you slightly finer +%control over how the daemon ought to run. This command will of course +%only be available when the \hgext{inotify} extension is enabled. + +\hgxcmd{inotify}{inserve}コマンドを使ってステータスデーモンを手動で実行す +ることも可能である．これにより，デーモンがどのように動作するのかをやや細 +かくコントロールすることができる．当然ながら，このコマンドは +\hgext{inotify}が有効の場合のみ利用可能である． + -When you're using the \hgext{inotify} extension, you should notice -\emph{no difference at all} in Mercurial's behaviour, with the sole -exception of status-related commands running a whole lot faster than -they used to. You should specifically expect that commands will not -print different output; neither should they give different results. -If either of these situations occurs, please report a bug. +%When you're using the \hgext{inotify} extension, you should notice +%\emph{no difference at all} in Mercurial's behaviour, with the sole +%exception of status-related commands running a whole lot faster than +%they used to. You should specifically expect that commands will not +%print different output; neither should they give different results. +%If either of these situations occurs, please report a bug. + +\hgext{inotify}拡張を使っている時はMercurialの\emph{全く変化なし}という動 +作に気付くだろう．ステータスに関係するコマンドは以前よりずっと高速になっ +ているという一つの例外を除いてコマンドは特別の出力も結果も出力しないこと +に留意されたい．何か特別なことが起きたらバグとして報告して欲しい． %\section{Flexible diff support with the \hgext{extdiff} extension} \section{\hgext{extdiff}拡張による柔軟なdiffサポート} diff -r b96d7f6504e5 -r ef197f25f11e ja/todo.txt --- a/ja/todo.txt Mon Sep 01 18:20:56 2008 +0900 +++ b/ja/todo.txt Tue Sep 02 17:27:11 2008 +0900 @@ -5,7 +5,7 @@ daily.tex filenames.tex hg_id.tex noneed -hgext.tex +hgext.tex 50% hook.tex intro.tex license.tex