RubyGems - rroonga - Versions diffs - 2.1.2-x86-mingw32 → 2.1.3-x86-mingw32 - Mend

rroonga 2.1.2-x86-mingw32 → 2.1.3-x86-mingw32

Files changed (788) hide show

data/vendor/local/share/doc/groonga/source/contribution/development/test.txt DELETED Viewed

@@ -1,116 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-テスト方法
-===========
-テスト環境の構築
-----------------
-Cutterのインストール
-^^^^^^^^^^^^^^^^^^^^
-groongaは、テストのフレームワークとして Cutter_ を用いています。
-Cutterのインストール方法は プラットフォーム毎のCutterのインストール方法_ をご覧下さい。
-.. _Cutter: http://cutter.sourceforge.net/
-.. _プラットフォーム毎のCutterのインストール方法: http://cutter.sourceforge.net/reference/ja/install.html
-lcovのインストール
-^^^^^^^^^^^^^^^^^^
-カバレッジ情報を計測するためには、lcov 1.6以上が必要です。DebianやUbuntuでは以下のようにしてインストールできます。::
- % sudo aptitude install -y lcov
-clangのインストール
-^^^^^^^^^^^^^^^^^^^
-ソースコードの静的解析を行うためには、clang(scan-build)をインストールする必要があります。DebianやUbuntuでは以下のようにしてインストールできます。::
- % sudo aptitude install -y clang
-libmemcachedのインストール
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-memcachedのバイナリプロトコルのテストを動作させるためには、libmemcachedの導入が必要です。squeeze以降のDebianやKarmic以降のUubntuでは以下の用にしてインストールできます。::
- % sudo aptitude install -y libmemcached-dev
-テストの動作
-------------
-groongaのトップディレクトリで、以下のコマンドを実行します。::
- make check
-カバレッジ情報
---------------
-groongaのトップディレクトリで、以下のコマンドを実行します。::
- make coverage
-すると、coverageディレクトリ以下に、カバレッジ情報が入ったhtmlが出力されます。
-カバレッジには、Lines/Functions/Branchesの3つの対象があります。それぞれ、行／関数／分岐に対応します。Functionsがもっとも重要な対象です。すべての関数がテストされるようになっていることを心がけてください。
-テストがカバーしていない部分の編集は慎重に行ってください。また、テストがカバーしている部分を増やすことも重要です。
-様々なテスト
-------------
-テストは、test/unitディレクトリにおいて、./run-test.shを実行することによっても行えます。run-test.shはいくつかのオプションをとります。詳細は、./run-test.sh --helpを実行しヘルプをご覧ください。
-特定のテスト関数のみテストする
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-特定のテスト関数(Cutterではテストと呼ぶ)のみをテストすることができます。
-実行例::
- % ./run-test.sh -n test_text_otoj
-特定のテストファイルのみテストする
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-特定のテストファイル(Cutterではテストケースと呼ぶ)のみテストすることができます。
-実行例::
- % ./run-test.sh -t test_string
-不正メモリアクセス・メモリリーク検出
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-環境変数CUTTER_CHECK_LEAKをyesと設定すると、valgrindを用いて不正メモリアクセスやメモリリークを検出しつつ、テストを動作させることができます。
-run-test.shのみならず、make checkでも利用可能です。
-実行例::
- % CUTTER_CHECK_LEAK=yes make check
-デバッガ上でのテスト実行
-^^^^^^^^^^^^^^^^^^^^^^^^
-環境変数CUTTER_DEBUGをyesと設定すると、テストが実行できる環境が整ったgdbが実行されます。gdb上でrunを行うと、テストの実行が開始されます。
-run-test.shのみならず、make checkでも利用可能です。
-実行例::
- % CUTTER_DEBUG=yes make check
-静的解析
---------
-scan-buildを用いて、ソースコードの静的解析を行うことができます。scan_buildというディレクトリに解析結果のhtmlが出力されます。::
- % scan-build ./configure --prefix=/usr
- % make clean
- % scan-build -o ./scan_build make -j4
-configureは１度のみ実行する必要があります。

data/vendor/local/share/doc/groonga/source/contribution/development.txt DELETED Viewed

@@ -1,12 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-groonga開発者向け情報
-=====================
-.. toctree::
-   :maxdepth: 1
-   :glob:
-   development/*

data/vendor/local/share/doc/groonga/source/contribution/documentation/c-api.txt DELETED Viewed

@@ -1,14 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-C API
-=====
-We still have C API documentation in include/groonga.h. But
-we want to move them into doc/source/c-api/\*.txt. We welcome
-to you help us by moving C API documentation.
-We will use `the C domain markup`_ of Sphinx.
-.. _the C domain markup: http://sphinx.pocoo.org/latest/domains.html#the-c-domain

data/vendor/local/share/doc/groonga/source/contribution/documentation/i18n.txt DELETED Viewed

@@ -1,198 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-I18N
-====
-We only had documentation in Japanese.  We start to support
-I18N documentation by gettext based `Sphinx I18N feature`_.
-We'll use English as base language and translate
-English into other languages such as Japanese. We'll put
-all documentations into doc/source/ and process them by
-Sphinx.
-.. _Sphinx I18N feature: http://sphinx.pocoo.org/latest/intl.html
-But we still use Japanese in doc/source/ for now. We need to
-translate Japanese documentation in doc/source/ into
-English. We welcome to you help us by translating
-documentation.
-Translation flow
-----------------
-After doc/source/\*.txt are updated, we can start translation.
-Here is a translation flow:
-1. Clone groonga repository.
-2. Update .po files.
-3. Edit .po files.
-4. Generate HTML files.
-5. Confirm HTML output.
-6. Repeat 2.-4. until you get good result.
-7. Send your works to us!
-Here are command lines to do the above flow. Following
-sections describes details.
-::
-  # Please fork https://github.com/groonga/groonga on GitHub
-  % git clone https://github.com/${YOUR_GITHUB_ACCOUNT}/groonga.git
-  % ./autogen.sh
-  % ./configure
-  % cd doc/locale/${LANGUAGE}/LC_MESSAGES # ${LANGUAGE} is language code such as 'ja'.
-  % make update # *.po are updated
-  % editor *.po # translate *.po # you can use your favorite editor
-  % cd ..
-  % make html
-  % browser html/index.html # confirm translation
-  % git add LC_MESSAGES/*.po
-  % git commit
-  % git push
-How to clone groonga repository
--------------------------------
-First, please fork groonga repository on GitHub. You
-just access https://github.com/groonga/groonga and press
-`Fork` button. Now you can clone your groonga repository::
-  % git clone https://github.com/${YOUR_GITHUB_ACCOUNT}/groonga.git
-Then you need to configure your cloned repository::
-  % cd groonga
-  % ./autogen.sh
-  % ./configure
-The above steps are just needed at the first setup.
-If you have troubles on the above steps, you can use source
-files available on http://packages.groonga.org/source/groonga/ .
-How to update .po files
------------------------
-You can update .po files by running `make update` on
-doc/locale/${LANGUAGE}/LC_MESSAGES. (Please substitute
-`${LANGUAGE}` with your language code such as 'ja'.)::
-  % cd doc/locale/ja/LC_MESSAGES
-  % make update
-How to edit .po
----------------
-There are some tools to edit .po files. .po files are just
-text. So you can use your favorite editor. Here is a
-specialized editor for .po file edit list.
-Emacs's po-mode_
-  It is bundled in gettext.
-Poedit_
-  It is a .po editor and works on many platform.
-gted
-  It is also a .po editor and is implemented as Eclipse plugin.
-.. _po-mode: http://www.gnu.org/s/hello/manual/gettext/PO-Mode.html
-.. _Poedit: http://www.poedit.net/
-.. _gted: http://www.gted.org/
-How to generate HTML files
---------------------------
-You can generate HTML files with updated .po files by
-running `make html` on doc/locale/${LANGUAGE}. (Please
-substitute `${LANGUAGE}` with your language code such as
-'ja'.)::
-  % cd doc/locale/ja/
-  % make html
-You can also generate HTML files for all languages by
-running `make html` on doc/locale::
-  % cd doc/locale
-  % make html
-.. note::
-   .mo files are updated automatically by `make html`. So
-   you don't care about .mo files.
-How to confirm HTML output
---------------------------
-HTML files are generated in
-doc/locale/${LANGUAGE}/html/. (Please substitute
-`${LANGUAGE}` with your language code such as 'ja'.) You can
-confirm HTML output by your favorite browser::
-  % firefox doc/locale/ja/html/index.html
-How to send your works
-----------------------
-We can receive your works via pull request on GitHub or
-E-mail attachment patch or .po files themselves.
-How to send pull request
-++++++++++++++++++++++++
-Here are command lines to send pull request::
-  % git add doc/locale/ja/LC_MESSAGES/*.po
-  % git commit
-  % git push
-Now you can send pull request on GitHub. You just access
-your repository page on GitHub and press `Pull Request`
-button.
-.. seealso:: `Help.GitHub - Sending pull requests`_.
-.. _Help.GitHub - Sending pull requests: http://help.github.com/pull-requests/
-How to send patch
-+++++++++++++++++
-Here are command lines to create patch::
-  % git add doc/locale/ja/LC_MESSAGES/*.po
-  % git commit
-  % git format-patch origin/master
-You can find 000X-YYY.patch files in the current
-directory. Please send those files to us!
-.. seealso:: :doc:`/community` describes our contact information.
-How to send .po files
-+++++++++++++++++++++
-Please archive doc/locale/${LANGUAGE}/LC_MESSAGES/ (Please
-substitute `${LANGUAGE}` with your language code such as
-'ja'.) and send it to us! We extract and merge them to the
-groonga repository.
-.. seealso:: :doc:`/community` describes our contact information.
-How to add new language
------------------------
-Here are command lines to add new translation language::
-  % cd doc/locale
-  % make add LOCALE=${LANGUAGE} # specify your language code such as 'de'.
-Please substitute `${LANGUAGE}` with your language code such
-as 'ja'.
-.. seealso:: `Codes for the Representation of Names of Languages`_.
-.. _Codes for the Representation of Names of Languages: http://www.loc.gov/standards/iso639-2/php/English_list.php

data/vendor/local/share/doc/groonga/source/contribution/documentation.txt DELETED Viewed

@@ -1,16 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-How to contribute in documentation topics
-=========================================
-We use Sphinx_ for documentation tool.
-.. _Sphinx: http://sphinx.pocoo.org/
-.. toctree::
-   :maxdepth: 1
-   :glob:
-   documentation/*

data/vendor/local/share/doc/groonga/source/contribution/report.txt DELETED Viewed

@@ -1,28 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-How to report a bug
-===================
-There are two ways to report a bug:
-  * Submit a bug to the issue tracker
-  * Report a bug to the mailing list
-You can use either way It makes no difference to us.
-Submit a bug to the issue tracker
----------------------------------
-Groonga project has two issue tracking systems, `Redmine
-<http://redmine.groonga.org/projects/groonga/issues>`_ and `GitHub
-issue tracker <https://github.com/groonga/groonga/issues>`_.  Redmine
-is for Japanese and GitHub issue tracker is for English. You can use
-one of them to report a bug.
-Report a bug to the mailing list
---------------------------------
-Groonga project has :doc:`/community` for discussing about groonga.
-Please send a mail that describes a bug.

data/vendor/local/share/doc/groonga/source/contribution.txt DELETED Viewed

@@ -1,26 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-How to contribute to groonga
-============================
-We welcome your contributions to the groonga project. There are many ways
-to contribute, such as using groonga, introduction to others, etc.
-For example, if you find a bug when using groonga, you are welcome to
-report the bug. Coding and documentation are also welcome for groonga and
-its related projects.
-As a user:
-  If you are interested in groonga, please read this document and try it.
-As a spokesman:
-  Please introduce groonga to your friends and colleagues.
-As a developer: Bug report, development and documentation
-  This section describes the details.
-.. toctree::
-   :maxdepth: 3
-   contribution/report
-   contribution/development
-   contribution/documentation

data/vendor/local/share/doc/groonga/source/development/travis-ci.txt DELETED Viewed

@@ -1,61 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-Travis CI
-=========
-This section describes about using groonga on `Travis CI
-<http://travis-ci.org/>`_. Travis CI is a hosted continuous
-integration service for the open source community.
-You can use Travis CI for your open source software. This section only
-describes about groonga related configuration. See `Travis CI:
-Documentation <http://about.travis-ci.org/docs/>`_ about general
-Travis CI.
-Configuration
--------------
-Travis CI is running on 32-bit Ubuntu 11.10. (See `Travis CI: About
-Travis CI Environment
-<http://about.travis-ci.org/docs/user/ci-environment/>`_.)  You can
-use apt-line for Ubuntu 11.10 provided by groonga project to install
-groonga on Travis CI.
-You can custom build lifecycle by ``.travis.yml``. (See `Travis CI:
-Conifugration your Travis CI build with .travis.yml
-<http://about.travis-ci.org/docs/user/build-configuration/>`_.) You
-can use ``before_install`` hook or ``install`` hook. You should use
-``before_install`` if your software uses a language that is supported
-by Travis CI such as Ruby. You should use ``install`` otherwise.
-Add the following ``before_install`` configuration to ``.travis.yml``::
-  before_install:
-    - curl https://raw.github.com/groonga/groonga/master/data/travis/setup.sh | sh
-If you need to use ``install`` hook instead of ``before_install``, you
-just substitute ``before_install:`` with ``install:``.
-With the above configuration, you can use groonga for your build.
-Examples
---------
-Here are open source softwares that use groonga on Travis CI:
-  * `rroonga <http://groonga.rubyforge.org/#about-rroonga>`_ (Ruby bindings)
-    * `rroonga on Travis CI <http://travis-ci.org/#!/ranguba/rroonga>`_
-    * `.travis.yml for rroonga <https://github.com/ranguba/rroonga/blob/master/.travis.yml>`_
-  * `nroonga <http://nroonga.github.com/>`_ (node.js bindings)
-    * `nroonga on Travis CI <http://travis-ci.org/#!/nroonga/nroonga>`_
-    * `.travis.yml for nroonga <https://github.com/nroonga/nroonga/blob/master/.travis.yml>`_
-  * `logaling-command <http://logaling.github.com/>`_ (A glossary management command line tool)
-    * `logaling-command on Travis CI <http://travis-ci.org/#!/logaling/logaling-command>`_
-    * `.travis.yml for logaling-command <https://github.com/logaling/logaling-command/blob/master/.travis.yml>`_

data/vendor/local/share/doc/groonga/source/development.txt DELETED Viewed

@@ -1,15 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-Development
-===========
-This section describes about developing with groonga. You may develop
-an application that uses groonga as its detabase, a library that uses
-libgroonga, language bindings of libgroonga and so on.
-.. toctree::
-   :maxdepth: 2
-   development/travis-ci

data/vendor/local/share/doc/groonga/source/example/completion-1.log DELETED Viewed

@@ -1,31 +0,0 @@
-Execution example::
-  suggest --table item_query --column kana --types complete --frequency_threshold 1 --query en
-  # [
-  #   [
-  #     0,
-  #     1337566253.89858,
-  #     0.000355720520019531
-  #   ],
-  #   {
-  #     "complete": [
-  #       [
-  #         1
-  #       ],
-  #       [
-  #         [
-  #           "_key",
-  #           "ShortText"
-  #         ],
-  #         [
-  #           "_score",
-  #           "Int32"
-  #         ]
-  #       ],
-  #       [
-  #         "engine",
-  #         1
-  #       ]
-  #     ]
-  #   }
-  # ]

data/vendor/local/share/doc/groonga/source/example/correction-1.log DELETED Viewed

@@ -1,31 +0,0 @@
-Execution example::
-  suggest --table item_query --column kana --types correction --frequency_threshold 1 --query saerch
-  # [
-  #   [
-  #     0,
-  #     1337566253.89858,
-  #     0.000355720520019531
-  #   ],
-  #   {
-  #     "correct": [
-  #       [
-  #         1
-  #       ],
-  #       [
-  #         [
-  #           "_key",
-  #           "ShortText"
-  #         ],
-  #         [
-  #           "_score",
-  #           "Int32"
-  #         ]
-  #       ],
-  #       [
-  #         "search",
-  #         1
-  #       ]
-  #     ]
-  #   }
-  # ]

data/vendor/local/share/doc/groonga/source/example/reference/commands/register/query_expanders_tsv.log DELETED Viewed

@@ -1,4 +0,0 @@
-Execution example::
-  register query_expanders/tsv
-  # [[0, 1337566253.89858, 0.000355720520019531], true]

data/vendor/local/share/doc/groonga/source/example/reference/commands/select/filter_equal.log DELETED Viewed

@@ -1,41 +0,0 @@
-Execution example::
-  select Entries --filter '_key == "Groonga"'
-  # [
-  #   [
-  #     0,
-  #     1337566253.89858,
-  #     0.000355720520019531
-  #   ],
-  #   [
-  #     [
-  #       [
-  #         1
-  #       ],
-  #       [
-  #         [
-  #           "_id",
-  #           "UInt32"
-  #         ],
-  #         [
-  #           "_key",
-  #           "ShortText"
-  #         ],
-  #         [
-  #           "content",
-  #           "Text"
-  #         ],
-  #         [
-  #           "n_likes",
-  #           "UInt32"
-  #         ]
-  #       ],
-  #       [
-  #         2,
-  #         "Groonga",
-  #         "I started to use groonga. It's very fast!",
-  #         10
-  #       ]
-  #     ]
-  #   ]
-  # ]

data/vendor/local/share/doc/groonga/source/example/reference/commands/select/filter_less_than.log DELETED Viewed

@@ -1,59 +0,0 @@
-Execution example::
-  select Entries --filter 'n_likes < 11'
-  # [
-  #   [
-  #     0,
-  #     1337566253.89858,
-  #     0.000355720520019531
-  #   ],
-  #   [
-  #     [
-  #       [
-  #         4
-  #       ],
-  #       [
-  #         [
-  #           "_id",
-  #           "UInt32"
-  #         ],
-  #         [
-  #           "_key",
-  #           "ShortText"
-  #         ],
-  #         [
-  #           "content",
-  #           "Text"
-  #         ],
-  #         [
-  #           "n_likes",
-  #           "UInt32"
-  #         ]
-  #       ],
-  #       [
-  #         1,
-  #         "The first post!",
-  #         "Welcome! This is my first post!",
-  #         5
-  #       ],
-  #       [
-  #         2,
-  #         "Groonga",
-  #         "I started to use groonga. It's very fast!",
-  #         10
-  #       ],
-  #       [
-  #         4,
-  #         "Good-bye Senna",
-  #         "I migrated all Senna system!",
-  #         3
-  #       ],
-  #       [
-  #         5,
-  #         "Good-bye Tritonn",
-  #         "I also migrated all Tritonn system!",
-  #         3
-  #       ]
-  #     ]
-  #   ]
-  # ]