| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
| |
Useful for verifying that our tar-file creation works. The tar-file
name can't easily be used as a target directly since it depends on the
current git revision.
|
| |
|
|
|
|
| |
Theese were previously pointing to "make VERSION=X.Y release", but
we've recently changed to an alternate scheme involving the updated
version in a file named "version".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We do this so that "git archive" produces a usable tar file without us
having to post-modify it, (since tools like git-buildpackage might not
give us an easy way to hook into the tar-file-creation step).
To support this we also have to change our preference to prefer the
git-described-based version (if available) and only if not available
do we fallback to using what's in the "version" file. Finally, we also
ovverride this preference when releasing, (where what's in the
"version" file wins).
Note that using our Makefile's rule to create a tar file still will
insert the git-based version into the tar file. This is useful for
creating snapshots which will correctly report the git version from
which they were created.
|
| |
|
|
|
| |
It's just too long for copy/paste, so just let the user know the name
of the file containing the message instead.
|
| |
|
|
| |
This was accidentally hard-coded to always print the 0.1 NEWS blurb.
|
| |
|
|
|
| |
Where by clean, we check that no files are known to git to be
modified.
|
| |
|
|
|
| |
I'm unlikely to always remember to pass VERSION=X.Y so it's nice for
make release to remind me.
|
| |
|
|
|
|
|
|
|
|
|
| |
We put verify-version as a dependency, not a recursive action to keep
its output clean, (I know that I will always type "make release"
instead of "make VERSION=X.Y release" so I want a nice, neat
reminder).
Also, put the various ssh-based commands together, and after the
build, (so that it doesn't ask for a password/passphrase both before
and after building).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, we had a separate release-upload target that a user might
mistake as something useful to call directly, (which would have the
undesired effect or uploading a new package, but without first making
all the checks that we want).
So we eliminate that target, (folding its actions into "make
release"), and we also rename the several release-verify-foo targets
to simply verify-foo. This leaves as the only targets with "release"
in the name as "release" and "release-message". Both of these are
intended for the user to call directly.
|
| |
|
|
| |
Just an extra word that clearly didn't belong.
|
| |
|
|
|
| |
This drops one manual step from our release process, (helping
to ensure we don't forget anything during the release).
|
| |
|
|
|
|
|
| |
I just wasted far too much time looking for a bug that wasn't actually
there only because I hadn't recompiled before running the test
suite. Now we can take advantage of actual dependency information to
force a rebuild for "make test".
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Apparently the OS X linker can't resolve symbols when linking a
program (notmuch) against a library (libnotmuch) when the library
depends on another library (libgmime) that the program doesn't depend
on directly.
For this case, we need to link the program directly against both
libraries, but we don't want to do this on Linux, where the linker can
do this on its own and the explicit, unneeded link would cause
problems.
|
| |
|
|
|
|
|
|
| |
This patch adds a configure check for OS X (actually Darwin),
and sets up the Makefiles to build a proper shared library on
that platform.
Signed-off-by: Aaron Ecay <aaronecay@gmail.com>
|
| |
|
|
| |
Since the library code needs these as well.
|
| |
|
|
|
|
|
| |
The recent change to include sub-directory Makefile.local files
before the top-level Makefile.local means that we need to include
the Makefile.config before those. So move it up from Makefile.local
to Makefile.
|
| |
|
|
|
|
|
|
|
|
|
| |
Must set extra_c(xx)flags before including subdir Makefile.local's,
so that there is a blank slate that the subdirs can add on to.
Must include subdir Makefile.local's before global one, otherwise
the compat sources are not added to the list of those to be
compiled.
Signed-off-by: Aaron Ecay <aaronecay@gmail.com>
|
| |
|
|
|
|
|
| |
Since the binaries contain C++ code, it is necessary to use the C++
linker, or errors result on some platforms (OS X).
Signed-off-by: Aaron Ecay <aaronecay@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When headers contain non-ASCII characters, they are encoded according
to rfc2047. Nomtuch reply command emits the headers in the encoded
form, which makes them hard to read by humans who compose the reply.
For example instead of "Subject: Re: Rozlučka" one currently sees
"Subject: Re: =?iso-8859-2?q?Rozlu=E8ka?=".
This patch adds a new GMime filter which is used to decode headers to
UTF-8 and uses this filter when notmuch reply outputs headers.
Signed-off-by: Michal Sojka <sojkam1@fel.cvut.cz>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I often have several versions of notmuch compiled and it would be very
helpful to be able to distinguish between them. Git has a very nice
feature to make intermediate numbering automatic and unambiguous so
let's use it here.
For tagged versions, the version is the name of the tag, for
intermediate versions, the unique ID of the commit is appended to the
tag name.
When notmuch is compiled from a release tarball, there is no git
repository and therefore the tarball contains a special file 'version',
which contains the version of release tarball.
To create a new release one has to run 'make release VERSION=X.Y'.
|
| |\
| |
| |
| |
| |
| |
| | |
These are the changes made between the notmuch 0.1 release and the
release of Debian version 0.1-1. It's mostly changes to the debian
directory, of course, but does also include some generally useful
Makefile improvements.
|
| | |
| |
| |
| |
| |
| | |
The libnotmuch.so library already does, so we don't need to do
it again. (Thanks to a Debian debhelper warning for pointing this
out.)
|
| | |
| |
| |
| |
| |
| | |
We currently don't distribute anything that's not already in git, so
there's no difference between these two targets, (but debhelper wants
to be able to call distclean).
|
| | |
| |
| |
| | |
Again, nothing tricky here.
|
| | |
| |
| |
| | |
For much better modularity.
|
| | |
| |
| |
| |
| |
| | |
Again, simplifying the interface to the Makefile. Installing these
files doesn't require bash nor zsh to actually be installed, so there's
little harm in just installing them unconditionally.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead, simply byte-compile the emacs source files as part of "make"
and install them as part of "make install". The byte compilation is
made conditional on the configure script finding the emacs binary.
That way, "make; make install" will still work for someone that doesn't
have emacs installed, (which was the only reason we had made a separate
"make install-emacs" target in the first place).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the original quiet function, there's an actual purpose (hiding
excessively long compiler command lines so that warnings and errors
from the compiler can be seen).
But with things like quiet_symlink there's nothing quieter. In fact
"SYMLINK" is longer than "ln -sf". So all this is doing is hiding the
actual command from the user for no real benefit.
The only actual reason we implemented the quiet_* functions was to be
able to neatly right-align the command name and left-align the arguments.
Let's give up on that, and just left-align everything, simplifying the
Makefiles considerably. Now, the only instances of a captialized command
name in the output is if there's some actually shortening of the command
itself.
|
| | |
| |
| |
| |
| |
| |
| | |
For other projects I release, there's a bunch of manual effort in
cosntructing the final release-announcement email. That's silly.
So automate this by extracting the appropirate text from NEWS and
by including a canned piece of the content from README.
|
| | |
| |
| |
| |
| | |
At the end of "make release" or at any point later with
"make release-message".
|
| | |
| |
| |
| | |
Otherwise I'm sure I'll always forget to push it.
|
| |\|
| |
| |
| |
| |
| |
| |
| | |
This is a merge of the few changes I made to release 0.1
retroactively, (after having incremented the version to 0.1.1).
Conflicts:
Makefile.local (renamed NOTMUCH_VERSION to VERSION)
|
| | |
| |
| |
| | |
And hopefully it actually works.
|
| | |
| |
| |
| |
| | |
So far just doing checks that the version is sane and that no release
of the same version already exists.
|
| |/
|
|
|
| |
After publishing the first notmuch release (0.1) to
http://notmuchmail.org/releases .
|
| |
|
|
| |
To create a versioned tar file for release.
|
| |
|
|
| |
Just to avoid any clash with files of the same names.
|
| |
|
|
|
|
|
|
|
| |
We add a magic line to the beginning of each Makefile.local file to
help the editor know that it should use makefile mode for editing the
file, (even though the filename isn't exactly "Makefile").
Edited-by: Carl Worth <cworth@cworth.org>: Expand treatment from
emacs/Makefile.local to each instance of Makefile.local.
|
| |
|
|
|
|
|
| |
Reviewed-by: Carl Worth <cworth@cworth.org>: Presumably, this is to
enable proper building in the very near-term future where the emacs
implementation consists of multiple files where some will `require'
functions from others.
|
| |
|
|
|
|
| |
It was getting quite annoying to see this big block of text on every
little build, (but I didn't want to get rid of it for any new users).
This seems to strike the right balance.
|
| |
|
|
|
| |
We're planning to do actual releases soon, so we need a version
number to put into the tar file.
|
| |
|
|
|
|
|
|
| |
The idea here is to allow a new user of notmuch to be able to run
notmuch immediately after compiling, (without having to install
the shared library first). This also ensures that the test suite
tests the locally compiled library, and not whatever installled
version of the library the dynamic linker happens to find.
|
| |
|
|
|
| |
With a carefully documented description of how to increment the
various version components.
|
| |
|
|
| |
Much better.
|
| |
|
|
|
| |
The output from make is looking better all the time, (though the
columns still aren't lined up).
|
| |
|
|
|
|
|
| |
The default "make" would be quite quiet, but still conveniently print
the CFLAGS. The explicit "make V=0" was intended to be identical, (only
not printing the message about V=1 but was broken in that it left the
CFLAGS off). Fix this.
|
| |
|
|
|
| |
These just made the output look so ugly, and weren't actually making
the rule definitions any simpler. Good riddance.
|
| |
|
|
|
|
| |
We had a fairly ugly violation of modularity with the top-level
Makefile.local isntalling everything, (even when the build commands
for the library were down in lib/Makefile.local).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
There's not any special configure logic for determining these variable
values, but if we did add some in the future, then these will now be
in the right place for that.
Additionally, this now makes Makefile.local the single place for the
user to look for manually tweaking a variable assignment, (say, for a
compiler that can't accept a particular warning argument).
With this change, there should rarely be any need for a user to poke
into any Makefile.local file.
|
| |
|
|
|
|
|
|
|
|
| |
Before it was impossible to know whether any particular setting or
rule definition was in Makefile or Makefile.local. So we strip the
Makefile down to little more than the list of sub-directories and
the logic to include all of the sub-directories' Makefile.local
fragments.
Then, all of the real work can happen inside of Makefile.local.
|
Carl Worth
Aaron Ecay
Michal Sojka
David Edmondson