From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: debian build-dependencies for testing should be marked <!nocheck>
Date: Thu, 10 Dec 2015 08:09:29 -0400 [thread overview]
Message-ID: <87zixiwlmu.fsf@zancas.localnet> (raw)
In-Reply-To: <87io47ny9b.fsf@alice.fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> hi notmuch people--
>
> debian/control's build-dependencies list a bunch of things that i think
> are only relevant for running the tests (e.g. dtach -- and maybe emacs
> and bash-completion and other packages).
>
> These should be marked <!nocheck> so that dpkg-buildpackage can know to
> ignore them when trying to build with BUILD_DEB_OPTIONS=nocheck.
>
> This is called a "build profile", if you want to look up more about it:
>
> https://wiki.debian.org/BuildProfileSpec
> https://bugs.debian.org/757760
>
> I'd send a patch, but i'm not entirely sure which packages are strictly
> for the build-time tests, so i hope someone with more experience with
> the debian package can mark them appropriately. Thanks!
Daniel and I chatted a bit on IRC, but for the record, other than lack
of time, my current concern about this is how well supported
build-profiles are supported on Debian stable. I haven't researched
this, but feedback is welcome.
BTW, bash completion is not there for the tests, nor is emacs (only) for
the tests. Emacs might be avoidable as a Debian build-dep (since Debian
does byte compilation at install time), but would come back if we switch
to "dh_elpa".
next prev parent reply other threads:[~2015-12-10 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 20:49 debian build-dependencies for testing should be marked <!nocheck> Daniel Kahn Gillmor
2015-12-10 12:09 ` David Bremner [this message]
2015-12-11 13:23 ` David Bremner
2015-12-11 13:25 ` Daniel Kahn Gillmor
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=87zixiwlmu.fsf@zancas.localnet \
--to=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).