buildroot/package/mutt, branch 2016.02

package/mutt: add optional support for libidn

2016-02-21T20:29:07+00:00

When libidn was compiled before, mutt will use it as optional dependency: $ output/host/usr/bin/x86_64-linux-readelf -a output/target/usr/bin/mutt | grep NEEDED 0x0000000000000001 (NEEDED) Shared library: [libncurses.so.5] 0x0000000000000001 (NEEDED) Shared library: [libidn.so.11] 0x0000000000000001 (NEEDED) Shared library: [libintl.so.8] 0x0000000000000001 (NEEDED) Shared library: [libc.so.1] Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

mutt: bump to version 1.5.24

2015-10-02T19:50:09+00:00

Switch to bitbucket since it's not hosted at sourceforge any more (and the official mutt source is ftp). Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

package/*: rename patches according to the new policy

2015-02-03T13:52:56+00:00

Autogenerated from rename-patch.py (http://patchwork.ozlabs.org/patch/403345) Signed-off-by: Samuel Martin Signed-off-by: Peter Korsgaard

package: add hashes for SourceForge-hosted packages

2014-12-28T21:21:16+00:00

Since SourceForge sometimes serves us faulty tarballs, we can tons of autobuild failures: http://autobuild.buildroot.org/results/9fb/9fba5bf086a4e7a29e5f7156ec43847db7aacfc4/ http://autobuild.buildroot.org/results/6c8/6c837b244c45ac3b3a887734a371cd6d226cf216/ ... Fix that by adding hash files for all SourceForge-hosted packages (thos etht did not already have it). We normally prefer to use hashes published by upstream, but hunting them all one by one is a tedious task, so those hashes were all locally computed with a script that searched for SF-hosted packages, downloades the associated tarball, computed the hash, and stored it in the corresponding .hash file. Also, SF publishes sha1 hashes, while I used the stronger sha256, since sha1 is now considered to be relatively weak. Signed-off-by: "Yann E. MORIN" Cc: Peter Korsgaard Cc: Thomas Petazzoni Cc: Maxime Hadjinlian Cc: Richard Braun Cc: Nathaniel Roach Signed-off-by: Thomas Petazzoni

package/mutt: specify the mailpath

2014-12-07T23:05:05+00:00

mutt's ./configure looks for different paths for where to look for incoming mails. This is absolutely worng in the case of cross-compilation, because the path it may find on the host may not exist on the target. Not only that, but some host may not even have any of the paths ./configure looks for. Fix that by specifying the mailpath, and set it to the value documented in the FHS [0] Since Buildroot only guarantees /tmp to be writable, make /var/mail a symlink to /tmp . [0] http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#VARMAILUSERMAILBOXFILES Reported-by: Vicente Olivert Riera Signed-off-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

package/mutt: do not run compiled programs from ./configure

2014-11-16T22:18:40+00:00

mutt's ./configure is broken for cross-compilation, because it runs programs to check for some features or behaviours. So, we have to feed it some variables to force the checks the way they are supposed to be resolved for our use-case. Fixes: http://autobuild.buildroot.net/results/58c/58c73e72e1387c7f490ad97a86666b12393917cf/ http://autobuild.buildroot.net/results/73b/73b8c54ca41cc475594c24a8d6176d511dcb85e6/ Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

packages: rename FOO_CONF_OPT into FOO_CONF_OPTS

2014-10-04T16:54:16+00:00

To be consistent with the recent change of FOO_MAKE_OPT into FOO_MAKE_OPTS, make the same change for FOO_CONF_OPT. Sed command used: find * -type f | xargs sed -i 's#_CONF_OPT\>#&S#g' Signed-off-by: Thomas De Schampheleire Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

mutt: Add options for imap/pop3 support, enable optional iconv/OpenSSL support

2014-04-14T21:35:47+00:00

[Thomas: keep a normal 'config' instead of 'menuconfig' for mutt.] Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

mutt: Bump version to 1.5.23

2014-04-14T21:21:03+00:00

removed upstream applied patch mutt-02-automake.patch http://dev.mutt.org/trac/changeset/0488deb39a35 Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

Config.in files: add missing dependencies to toolchain option comments

2013-11-10T22:59:57+00:00

When a package A depends on config option B and toolchain option C, then the comment that is given when C is not fulfilled should also depend on B. For example: config BR2_PACKAGE_A depends on BR2_B depends on BR2_LARGEFILE depends on BR2_WCHAR comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR This comment should actually be: comment "A needs a toolchain w/ largefile, wchar" depends on BR2_B depends on !BR2_LARGEFILE || !BR2_WCHAR or if possible (typically when B is a package config option declared in that same Config.in file): if BR2_B comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR [other config options depending on B] endif Otherwise, the comment would be visible even though the other dependencies are not met. This patch adds such missing dependencies, and changes existing such dependencies from depends on BR2_BASE_DEP && !BR2_TOOLCHAIN_USES_GLIBC to depends on BR2_BASE_DEP depends on !BR2_TOOLCHAIN_USES_GLIBC so that (positive) base dependencies are separate from the (negative) toolchain dependencies. This strategy makes it easier to write such comments (because one can simply copy the base dependency from the actual package config option), but also avoids complex and long boolean expressions. Signed-off-by: Thomas De Schampheleire Acked-by: Arnout Vandecappelle (Essensium/Mind) (untested) Signed-off-by: Peter Korsgaard