addpkg(main/mutt-wizard): A system for automatically configuring mutt...

[ghost]

... and isync with a simple interface and safe passwords

This program basically just works in Termux, only needing one minor change, and a pending PR upstream (developer seems to be on haitus).

I haven't tested to see if my build.sh/patches work as I'm not really a coder. Making this PR hoping someone else can polish it and finally get this added!

[TomJo2000]

I can't seem to find a package request for this project.
So I'll just go through an abbreviated version of the package request checklist below really quick.

Note

For future reference, please open a package request before spending the time to write a package build.

Package requests give us a heads up to evaluate if a package is suitable for packaging in the main Termux repositories.
^{https://github.com/termux/termux-packages/issues/new?template=02-package-request.yml}

Not all projects will meet out packaging guidelines.
In case this project does not, it may still be suitable for inclusion in the TUR

Packaging policy acknowledgement

• The project is actively developed.

• The project has existing packages and is "well known".

• Licensed under an open source license.

• [~] Not available through a language package manager: pip, npm, cpan, cargo, etc.

• Not taking up too much disk space (< 100MiB per architecture, exceptions can be made)

• Not duplicating the functionality of existing packages.

• Not serving hacking, malware, phishing, spamming, spying, ddos functionality.

• I certify that I have read Termux Packaging Policy and understand that my request will be denied if it is found lacking.

---

This package is a slightly odd case seeing as it's mostly written in mostly in Bash.
It still subjectively passes the, "requiring patches or modification to work", carve out for portable scripts.

But this package is probably a better fit for the TUR, since I can't seem to find any existing packages for muttwizard.
It also seems that there is a significant amount of new changes to the project that are not yet part of any stable release.
^{LukeSmithxyz/mutt-wizard@v3.3.1...master}

[ghost]

Didn't think of the TUR. mw is on the AUR (mutt-wizard-git), so I agree it's a better fit for the TUR. Thanks for telling me. I'll open a request there before making a PR this time.

Also didn't notice the stable-master difference. I installed and have it working on my device from the master branch. If I changed the source url to master, what should I put the version as, or should I not do that?

[TomJo2000]

Didn't think of the TUR. mw is on the AUR (mutt-wizard-git), so I agree it's a better fit for the TUR. Thanks for telling me. I'll open a request there before making a PR this time.

Also didn't notice the stable-master difference. I installed and have it working on my device from the master branch. If I changed the source url to master, what should I put the version as, or should I not do that?

We usually use a ${VERSION}-p${_COMMIT_DATE} structure for such cases.

termux-packages/packages/gnushogi/build.sh

Lines 5 to 7 in b1f4835

	_COMMIT=5bb0b5b2f6953b3250e965c7ecaf108215751a74
	_COMMIT_DATE=20141119
	TERMUX_PKG_VERSION=1.4.2-p${_COMMIT_DATE}

[ghost]

Thanks!