From: Jeffrey Ollie <jeff@ocjtech.us>
To: Bart Trojanowski <bart@jukie.net>,
Not Much Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Add SCons build files.
Date: Sun, 22 Nov 2009 10:00:26 -0600 [thread overview]
Message-ID: <935ead450911220800r47284335n301a2b2432638c72@mail.gmail.com> (raw)
In-Reply-To: <20091122141501.GH17268@jukie.net>
The SCons build files are not meant to require emacs. If I've messed
something up and emacs is somehow required I would consider that a bug
and would try to fix it.
As far as availability, I'm sure that SCons is one yum or apt-get or
<insert other package management system command> away. The only
people that would face more than a minor inconvenience are people that
prefer to download tarballs and compile and install things themselves.
Yes, I'm sure that make is widely available, but as notmuch gets used
on a wider variety of systems some sort of configuration system will
become necessary. If I can prevent another project from going down
the autoconf/automake path I'll be happy. I started creating CMake
build files but I don't know CMake well enough to come up with a
working build.
On 11/22/09, Bart Trojanowski <bart@jukie.net> wrote:
> * Jeffrey C. Ollie <jeff@ocjtech.us> [091122 08:47]:
>> The SCons build files included here *should* do everything that the
>> current Makefiles do, plus a little bit of configuration checking. To
>> build/install:
>
> Wouldn't that have the unfortunate side effect of making notmuch
> unusable w/o emacs and scons installed?
>
> GNU make has a much wider install base, and notmuch is still very useful
> without emacs.
>
> -Bart
>
> --
> WebSig: http://www.jukie.net/~bart/sig/
>
--
Sent from my mobile device
Jeff Ollie
next prev parent reply other threads:[~2009-11-22 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 13:47 [PATCH] Add SCons build files Jeffrey C. Ollie
2009-11-22 14:15 ` Bart Trojanowski
2009-11-22 16:00 ` Jeffrey Ollie [this message]
2009-11-22 17:21 ` Jed Brown
2009-11-22 20:02 ` Jeffrey Ollie
2009-11-22 20:36 ` Bart Trojanowski
2009-11-22 20:43 ` Ingmar Vanhassel
2009-11-23 3:11 ` Carl Worth
2009-11-23 4:36 ` Jeffrey Ollie
2009-11-23 6:20 ` Carl Worth
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=935ead450911220800r47284335n301a2b2432638c72@mail.gmail.com \
--to=jeff@ocjtech.us \
--cc=bart@jukie.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).