Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mutt recipe #699

Merged
merged 1 commit into from Dec 26, 2016
Merged

mutt recipe #699

merged 1 commit into from Dec 26, 2016

Conversation

extrowerk
Copy link
Member

For the sake of IMAP.
Sadly gmail requires SASL.

2000-2004 Edmund Grimley Evans
2006-2009 Rocco Rutte
2014-2015 Kevin J. McCarthy
"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quote goes on previous line. And all the continuation COPYRIGHT lines should be indented by 1 tab.

DESCRIPTION="A text-based email client for Unix-like systems. \
It was originally written by Michael Elkins in 1995 and released \
under the GNU General Public License version 2 or any later \
version.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Put it into previous line

PATCHES="mutt-$portVersion.patchset"

ARCHITECTURES="?x86_gcc2 x86 ?arm"
SECONDARY_ARCHITECTURES="?x86_gcc2 x86 ?arm"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can drop the ?arm in SECONDARY_ARCHITECTURES.

cmd:bison
cmd:gawk
cmd:gcc$secondaryArchSuffix
cmd:make
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to add a cmd:libtoolize$secondaryArchSuffix to BUILD_PREREQUIRES. The best place for it is just before cmd:make.
BTW, the cmd:gpgme_config$secondaryArchSuffix currently in BUILD_REQUIRES would be better in BUILD_PREREQUIRES, between the cmd:gcc$secondaryArchSuffix and the cmd:libtoolize$secondaryArchSuffix.

under the GNU General Public License version 2 or any later version.

The Mutt slogan is All mail clients suck. This one just sucks less."
HOMEPAGE="http://www.mutt.org"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO it would be better to have

HOMEPAGE="http://www.mutt.org/"

I know most browsers hide the trailing slash when there is nothing after it, but, to be correct, a URL needs either a path or a trailing slash.
I also know that this is a detail and that some recipes are missing that trailing slash.
But I think we should have correct URLs in our recipes.
A practical reason for keeping the slash is that when wrong URLs are copy/pasted to forums that make hyperlinks with them, these hyperlinks do not always work because the wrapper that creates the hyperlinks is not able to correctly detect the end of the domain name when it is followed by a dot. I've already seen that in some places. This never happens with correct URLs ;-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, thanks!

@waddlesplash waddlesplash merged commit 6661b5e into haikuports:master Dec 26, 2016
dacianf pushed a commit to dacianf/haikuports that referenced this pull request Jan 9, 2017
korli pushed a commit to korli/haikuports that referenced this pull request Jan 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants