RPM spec file

RPM spec file

[Jeffrey C. Ollie]

I prefere managing all of the software on my system with RPM, so I
came up with a quick spec file for building RPMS.  Once notmuch
settles down and I continue using it I may submit notmuch to Fedora as
an official package.  If you'd like your own RPMS build your own, I
don't plan on offering a repository of binary packages.

[PATCH] notmuch build: add a RPM spec file

[Jeffrey C. Ollie]

Add a spec file for building RPM packages.

Signed-off-by: Jeffrey C. Ollie <jeff@ocjtech.us>
---
 notmuch.spec |  110 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 110 insertions(+), 0 deletions(-)
 create mode 100644 notmuch.spec

diff --git a/notmuch.spec b/notmuch.spec
new file mode 100644
index 0000000..cca3a1b
--- /dev/null
+++ b/notmuch.spec
@@ -0,0 +1,110 @@
+%global git 306635c2
+
+%if %($(pkg-config emacs) ; echo $?)
+%global emacs_version 23.1
+%global emacs_lispdir %{_datadir}/emacs/site-lisp
+%global emacs_startdir %{_datadir}/emacs/site-lisp/site-start.d
+%else
+%global emacs_version %(pkg-config emacs --modversion)
+%global emacs_lispdir %(pkg-config emacs --variable sitepkglispdir)
+%global emacs_startdir %(pkg-config emacs --variable sitestartdir)
+%endif
+
+Name:           notmuch
+Version:        0.0
+Release:        0.3.%{git}%{?dist}
+Summary:        Not much of an email program
+
+Group:          Applications/Internet
+License:        GPLv3+
+URL:            http://notmuchmail.org/
+
+#
+# To create a tarball:
+#
+# git clone git://notmuchmail.org/git/notmuch
+# cd notmuch
+# git archive --format=tar --prefix=notmuch/ HEAD | bzip2 > notmuch-`git show-ref --hash=8 HEAD`.tar.bz2
+#
+Source0:        notmuch-%{git}.tar.bz2
+BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+
+BuildRequires:  xapian-core-devel
+BuildRequires:  gmime-devel
+BuildRequires:  libtalloc-devel
+BuildRequires:  zlib-devel
+BuildRequires:  emacs-el
+BuildRequires:  emacs-nox
+
+Requires:       emacs(bin) >= %{emacs_version}
+
+%description
+* "Not much mail" is what Notmuch thinks about your email
+  collection. Even if you receive 12000 messages per month or have on
+  the order of millions of messages that you've been saving for
+  decades. Regardless, Notmuch will be able to quickly search all of
+  it. It's just plain not much mail.
+
+* "Not much mail" is also what you should have in your inbox at any
+  time. Notmuch gives you what you need, (tags and fast search), so
+  that you can keep your inbox tamed and focus on what really matters
+  in your life, (which is surely not email).
+
+* Notmuch is an answer to Sup. Sup is a very good email program
+  written by William Morgan (and others) and is the direct inspiration
+  for Notmuch. Notmuch began as an effort to rewrite
+  performance-critical pieces of Sup in C rather than ruby. From
+  there, it grew into a separate project. One significant contribution
+  Notmuch makes compared to Sup is the separation of the
+  indexer/searcher from the user interface. (Notmuch provides a
+  library interface so that its indexing/searching/tagging features
+  can be integrated into any email program.)
+
+* Notmuch is not much of an email program. It doesn't receive messages
+  (no POP or IMAP suport). It doesn't send messages (no mail composer,
+  no network code at all). And for what it does do (email search) that
+  work is provided by an external library, Xapian. So if Notmuch
+  provides no user interface and Xapian does all the heavy lifting,
+  then what's left here? Not much.
+
+Notmuch is still in the early stages of development, but it does
+include one user interface, (implemented within emacs), which has at
+least two users using it for reading all of their incoming mail. If
+you've been looking for a fast, global-search and tag-based email
+reader to use within emacs, then Notmuch may be exactly what you've
+been looking for.
+
+Otherwise, if you're a developer of an existing email program and
+would love a good library interface for fast, global search with
+support for arbitrary tags, then Notmuch also may be exactly what
+you've been looking for.
+
+%prep
+%setup -q -n notmuch
+
+%build
+make %{?_smp_mflags} CFLAGS="%{optflags}"
+emacs -batch -f batch-byte-compile notmuch.el
+
+%install
+rm -rf %{buildroot}
+make install DESTDIR=%{buildroot} prefix=%{_prefix}
+mkdir -p %{buildroot}%{emacs_startdir}
+install -m0644 -p notmuch.el* %{buildroot}%{emacs_startdir}
+
+%clean
+rm -rf %{buildroot}
+
+%files
+%defattr(-,root,root,-)
+%doc AUTHORS COPYING COPYING-GPL-3 INSTALL README TODO
+
+%{_sysconfdir}/bash_completion.d/notmuch
+%{_bindir}/notmuch
+%{_mandir}/man1/notmuch.1*
+%{emacs_startdir}/notmuch.el*
+
+%changelog
+* Wed Nov 18 2009 Jeffrey C. Ollie <jeff@ocjtech.us> - 0.0-0.3.306635c2
+- First version
+
-- 
1.6.5.2

Re: RPM spec file

[Carl Worth]

On Wed, 18 Nov 2009 12:31:53 -0600, "Jeffrey C. Ollie" <jeff@ocjtech.us> wrote:
> I prefere managing all of the software on my system with RPM, so I
> came up with a quick spec file for building RPMS.  Once notmuch
> settles down and I continue using it I may submit notmuch to Fedora as
> an official package.  If you'd like your own RPMS build your own, I
> don't plan on offering a repository of binary packages.

This sounds great, Jeffrey.

What makes the most sense for this file? Shall we just leave it in the
central repository? Or put it in its own rpm branch? I'm open to your
suggestions here.

-Carl

Re: RPM spec file

[Jeffrey Ollie]

On Wed, Nov 18, 2009 at 7:03 PM, Carl Worth <cworth@cworth.org> wrote:
> On Wed, 18 Nov 2009 12:31:53 -0600, "Jeffrey C. Ollie" <jeff@ocjtech.us> wrote:
>> I prefere managing all of the software on my system with RPM, so I
>> came up with a quick spec file for building RPMS.  Once notmuch
>> settles down and I continue using it I may submit notmuch to Fedora as
>> an official package.  If you'd like your own RPMS build your own, I
>> don't plan on offering a repository of binary packages.
>
> This sounds great, Jeffrey.
>
> What makes the most sense for this file? Shall we just leave it in the
> central repository? Or put it in its own rpm branch? I'm open to your
> suggestions here.

I don't think that a separate Git branch makes sense, but maybe stuff
like this should be in a subdirectory like "packaging/fedora", since I
imagine that there will eventually be a need for "packaging/debian"
etc. as well.

-- 
Jeff Ollie

Re: RPM spec file

[Carl Worth]

On Thu, 19 Nov 2009 00:56:22 -0600, Jeffrey Ollie <jeff@ocjtech.us> wrote:
> I don't think that a separate Git branch makes sense, but maybe stuff
> like this should be in a subdirectory like "packaging/fedora", since I
> imagine that there will eventually be a need for "packaging/debian"
> etc. as well.

OK, Done.

Thanks again!

-Carl