unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>,
	Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Build-Depend on libgmime-2.6-dev | libgmime2.4-dev
Date: Fri, 10 Feb 2012 22:57:07 +0200	[thread overview]
Message-ID: <m2sjii5rvg.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87lioaesmu.fsf@rocinante.cs.unb.ca>

On Fri, 10 Feb 2012 09:15:53 -0400, David Bremner <david@tethera.net> wrote:
> On Thu,  9 Feb 2012 18:20:20 -0500, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> > libgmime-2.6-dev entered debian unstable today.  If 2.6 is available,
> > notmuch should build against 2.6 instead of 2.4, as 2.6 is the current
> > upstream stable version of libgmime.
> 
> Hi Daniel;
> 
> I'm not necessarily opposed to migrating to the Debian packages to gmime
> 2.6, but I'd like to point out that your patch is might be more decisive
> than intended, since the build daemons strip all but the first
> dependency. This will cause the build do fail if 2.6 is not
> available. For more discussion of this, see
> id:"20110920181701.GQ3245@codelibre.net" (debian-devel, Sept. 2011).

For the time being, should the order be:

- libgmime-2.4-dev,
+ libgmime-2.4-dev | libgmime-2.6-dev,

?

> 
> David

Tomi

  parent reply	other threads:[~2012-02-10 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 23:20 [PATCH] Build-Depend on libgmime-2.6-dev | libgmime2.4-dev Daniel Kahn Gillmor
2012-02-10 13:15 ` David Bremner
2012-02-10 17:58   ` Daniel Kahn Gillmor
2012-02-10 20:57   ` Tomi Ollila [this message]
2012-02-10 21:02     ` Daniel Kahn Gillmor
2012-02-28  2:25 ` David Bremner

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=m2sjii5rvg.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --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).