On Wed, May 14 2014, Wael M. Nasreddine wrote: > You can access the dashboard at https://travis-ci.org/notmuch/notmuch > --- > .travis.yml | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > create mode 100644 .travis.yml > > diff --git a/.travis.yml b/.travis.yml > new file mode 100644 > index 0000000..e8c3011 > --- /dev/null > +++ b/.travis.yml > @@ -0,0 +1,12 @@ > +language: c > +before_install: > + - sudo apt-get update -qq > + - wget 'https://launchpad.net/ubuntu/+archive/primary/+files/zlib1g-dev_1.2.8.dfsg-1ubuntu1_amd64.deb' > + - wget 'https://launchpad.net/ubuntu/+archive/primary/+files/zlib1g_1.2.8.dfsg-1ubuntu1_amd64.deb' > + - sudo dpkg -i zlib1g-dev_1.2.8.dfsg-1ubuntu1_amd64.deb > zlib1g_1.2.8.dfsg-1ubuntu1_amd64.deb Wael, I don't know much at all about travis (I gather that it's some sort of continuous integration test tool), but grabbing very specific zlib packages from a place on the 'net and then installing them seems fragile. - What happens when those are no longer the right version numbers? - What happens when those versions are already provided by the standard repository? - What happens when newer versions are provided by the standard repository? - What happens if travis runs start happening on (say) an arm64 machine? I realise that you might answer "I will keep this up to date", but we have to worry about what happens if you lose interest and wander away. What is required to get the updated (as I presume that is what they are) versions of zlib into the normal package repositories? Is it possible to specify that travis should use the equivalent of Debian testing or experimental repositories? > + - sudo apt-get install -f > + - sudo apt-get install dtach libxapian-dev libgmime-2.6-dev libtalloc-dev python-sphinx > + > +script: make test > +notifications: > + irc: "chat.freenode.net#notmuch" > -- > 1.9.1.423.g4596e3a > > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch