notmuch/Makefile.local, branch 0.7_rc1 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.7_rc1 2011-07-29T16:56:52Z build-system: Add pre-release target 2011-07-29T16:56:52Z David Bremner bremner@unb.ca 2011-07-29T15:45:12Z urn:sha1:839b7f20f620b365c5a918691e8f84095884d2d9 This is a lighter weight version of the release target, intended to support uploading release candidates to Debian. As a side effect, filter ~ out of VERSION to make tag names. build-system: tag debian-version as part of the release target 2011-07-17T14:20:51Z David Bremner bremner@debian.org 2011-07-17T14:18:10Z urn:sha1:2d69aba586b52566f322a347d459503d53de6ce6 This allows, e.g. gitpkg debian/0.x-1 to do the right thing. It also helps enforce the convention that Debian upload -1 is identical to the release tarball. build-system: update version check to support non-native packages. 2011-07-17T14:04:08Z David Bremner bremner@debian.org 2011-07-17T14:04:08Z urn:sha1:0897209f4d0609eb5ccd8cdf759f8d174c013566 We could be a bit more flexible about this and support optional Debian versions, but for the moment, we pick a policy and stick to it. build-system: guard parts irrevokable parts of release target with REALLY_UPLOAD 2011-07-17T13:59:41Z David Bremner bremner@debian.org 2011-07-04T11:39:04Z urn:sha1:466f3b57aa9650cbed47152241813e212c965f94 This supports both testing and use by non-upload privileged users. Along with previous commits in the series, this lets one do a dry run of the release process and created a tarball, signature file, and release announcement to inspect before uploading. build-system: use signed tag to make tar file, if available. 2011-07-17T13:59:41Z David Bremner bremner@debian.org 2011-07-03T20:28:47Z urn:sha1:9b0dfd11c5d4af6dc4cd2b79f33e0d6c460d414e This as the advantage that "make VERSION=n.m dist" will work correctly even if the wrong branch happens to be checked out. build-system: tag earlier in the release process. 2011-07-17T13:59:41Z David Bremner bremner@debian.org 2011-07-03T20:06:05Z urn:sha1:60173feb065a4306dc91093d886bf46475c23e11 If tagging fails, we really don't want to upload tarballs. build-system: remove use of git-buildpackage, dput. Add pristine-tar. 2011-07-17T13:59:41Z David Bremner bremner@debian.org 2011-07-17T12:55:50Z urn:sha1:939c91b7efbde03e8f51d71aa7e6654946b2bf33 The previous setup was dependent on the git-buildpackage configuration to find the resulting tar file, and consequently a bit fragile. We use pristine-tar instead to save a checksum-identical copy of the tar file. This will also faciliate "non-native" debian packages, if desired. dput again depends on the local configuration, and mainly is a bit too brave for me to do automatically. build-system: run make clean before testing. 2011-07-17T13:59:41Z David Bremner bremner@debian.org 2011-07-17T12:52:05Z urn:sha1:9fb9fb2986741041e37c2c65108b2031272b9b0b The reasoning is that we might have some error in the build system that causes something not to be rebuilt; this would potentially have the tests run on the wrong version of the code. build-system: replace use of ssh with wget for checking the website 2011-07-17T13:59:41Z David Bremner bremner@debian.org 2011-07-03T18:18:30Z urn:sha1:2e136988129507a6a8cbac62014122051f156072 The idea is to see if the version we are already releasing exists on the notmuch website. Using wget allows more people to run this target, and also allows people with ssh access to run it without access to their keys. Use stock GMimeSession by default 2011-06-04T00:42:54Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2011-06-03T23:57:46Z urn:sha1:5143e5e840b5e9d95611f57fdc9d4b27af6f0564 Our use of GMimeSession was unneeded boilerplate, and we weren't doing anything with it. This simplifies and clarifies that assumption. If we want to do anything fancier later, the examples in the gmime source are a reasonable source to work from in defining a new GMimeSession derivative. Since GMimeSession is going away in GMime 2.6, though, i don't recommend using it.