unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: notmuch release 0.20.2 now available
Date: Tue, 30 Jun 2015 10:40:18 +0200	[thread overview]
Message-ID: <20150630084018.GO24926@chitra.no-ip.org> (raw)
In-Reply-To: <87a8vhlkdv.fsf@maritornes.cs.unb.ca>

Hi David,

On Tue, Jun 30, 2015 at 09:34:36AM +0200, David Bremner wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> > On Tue, Jun 30, 2015 at 07:24:28AM +0200, David Bremner wrote:
> >> 
> >> Where to obtain notmuch 0.20.2
> >> ===========================
> >>   http://notmuchmail.org/releases/notmuch-0.20.2.tar.gz
> >
> > I took a quick pass at building the release for Fedora.  The ruby
> > bindings seem to fail to build (actually linking fails).
> >
> 
> The ruby bindings are not built automatically by 0.20.2.  You seem to be
> building a snapshot of master. If you want to build the release from
> git, use the signed tag.

Yes, I was aware.  I tried again with proper 0.20.2.  And everything
succeeds.  So I guess something with master.  I usually build master in
that repo, I guess I'll stick to the release for now.

> The question of why master won't build for you is also interesting, but
> a different question. A quick search reveals packages of notmuch 0.19
> ruby bindings seemingly for fc22
> 
>      https://apps.fedoraproject.org/packages/ruby-notmuch/contents
> 
> So I guess have a look and see what existing fedora packaging does.

Yes, I have looked at what the official packages[1] do, I do exactly the
same[2].  Essentially the spec file does the following:

  pushd bindings/ruby
      ruby extconf.rb --vendor --with-cflags="%{optflags}"
      make %{?_smp_mflags}
  popd

where, _smp_mflags is -jN, and optflags is options for gcc.  If you need
the specific flags, I can try to look it up.

> At the moment the only way to disable the ruby bindings (other than
> hacking the build system) is not to have the ruby development files in
> the build env. This may change by the time this is part of a release.

Since everything is built in a chroot, I have control over the build
environment via the spec file.  If need be, I can disable it.  However
it would be interesting to know why master fails.

Thanks for your comments.

Cheers,

Footnotes:

[1] http://pkgs.fedoraproject.org/cgit/notmuch.git/tree/notmuch.spec#n137
[2] https://github.com/suvayu/notmuch-spec/blob/master/notmuch.spec#L139

-- 
Suvayu

Open source is the future. It sets us free.

  reply	other threads:[~2015-06-30  8:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  5:24 notmuch release 0.20.2 now available David Bremner
2015-06-30  6:39 ` Suvayu Ali
2015-06-30  7:34   ` David Bremner
2015-06-30  8:40     ` Suvayu Ali [this message]
2015-06-30 17:02       ` David Bremner
2015-07-06 14:04         ` Suvayu Ali

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150630084018.GO24926@chitra.no-ip.org \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).