notmuch.git  about / heads / tags
Unnamed repository; edit this file 'description' to name the repository.
   commit 29762dd15e84da6c4a30016b255e7dba8002cf8a (patch)
   parent 0eb42137 debian: build notmuch-vim again
     tree e6ea6d61b7bb20c4710f73cba368e1c4e8cfb2e7
   author David Bremner <bremner@debian.org>  2013-07-28 14:08:00 -0300
committer David Bremner <bremner@debian.org>  2013-07-28 14:28:25 -0300

debian: rename notmuch-ruby to ruby-notmuch

This seems more in line with

http://wiki.debian.org/Teams/Ruby/Packaging#Guidelines_for_Ruby_packaging
---
 debian/control                                        | 4 ++--
 debian/{notmuch-ruby.install => ruby-notmuch.install} | 0
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 4fd8e0d5..74a51614 100644
--- a/debian/control
+++ b/debian/control
@@ -90,7 +90,7 @@ Description: Python 3 interface to the notmuch mail search and index library
  This package provides a Python 3 interface to the notmuch
  functionality, directly interfacing with a shared notmuch library.
 
-Package: notmuch-ruby
+Package: ruby-notmuch
 Architecture: any
 Section: ruby
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -125,7 +125,7 @@ Architecture: all
 Section: mail
 Breaks: notmuch (<<0.6~254~)
 Replaces: notmuch (<<0.6~254~)
-Depends: ${misc:Depends}, notmuch, vim-addon-manager, vim-ruby, notmuch-ruby
+Depends: ${misc:Depends}, notmuch, vim-addon-manager, vim-ruby, ruby-notmuch
 Recommends: ruby-mail
 Description: thread-based email index, search and tagging (vim interface)
  Notmuch is a system for indexing, searching, reading, and tagging
diff --git a/debian/notmuch-ruby.install b/debian/ruby-notmuch.install
similarity index 100%
rename from debian/notmuch-ruby.install
rename to debian/ruby-notmuch.install


glossary
--------
Commit objects reference one tree, and zero or more parents.

Single parent commits can typically generate a patch in
unified diff format via `git format-patch'.

Multiple parents means the commit is a merge.

Root commits have no ancestor.  Note that it is
possible to have multiple root commits when merging independent histories.

Every commit references one top-level tree object.

git clone https://yhetil.org/notmuch.git