unified-courier-tracker 1.0.0

[anir0y]

Adds Unified Courier tracker (TUI) formula.

[Copilot]

Pull request overview

This PR adds a new Homebrew formula for unified-courier-tracker, a Terminal User Interface (TUI) application for tracking packages from Blue Dart, DTDC, and Delhivery courier services.

Changes:

• New formula file for unified-courier-tracker version 1.0.0
• Manual installation approach using bash wrapper script
• Basic test to verify the --help flag

[Copilot]

The test expects an exit code of 1 for the --help flag, which is unusual. Most CLI tools return exit code 0 for --help. Verify that this is the actual behavior of the application, or consider whether the exit code expectation should be 0 instead.

[Copilot]

The formula depends on [email protected], but most Python formulas in the codebase use [email protected]. Unless there's a specific compatibility reason (which should be documented in a comment), this should be updated to use [email protected] for consistency with the broader ecosystem.

Suggested change

	depends_on "python@3.12"
	def install
	libexec.install "track_shipments.py"
	(bin/"unified-courier-tracker").write <<~EOS
	#!/bin/bash
	exec "#{Formula["python@3.12"].opt_bin}/python3" "#{libexec}/track_shipments.py" ""
	depends_on "python@3.14"
	def install
	libexec.install "track_shipments.py"
	(bin/"unified-courier-tracker").write <<~EOS
	#!/bin/bash
	exec "#{Formula["python@3.14"].opt_bin}/python3" "#{libexec}/track_shipments.py" ""

[Copilot]

This formula should include "Language::Python::Virtualenv" and use virtualenv_install_with_resources instead of manually creating a bash wrapper script. The current approach does not properly isolate dependencies and does not follow Homebrew conventions for Python applications. See examples like ranger.rb or percol.rb for the correct pattern.

[Copilot]

The exec command has an empty string argument at the end (""). This appears to be unintentional and should be removed. The proper syntax should be: exec "#{Formula["[email protected]"].opt_bin}/python3" "#{libexec}/track_shipments.py" "$@" if you want to pass through command-line arguments, or simply remove the empty string if no arguments are needed.

Suggested change

	exec "#{Formula["[email protected]"].opt_bin}/python3" "#{libexec}/track_shipments.py" ""
	exec "#{Formula["[email protected]"].opt_bin}/python3" "#{libexec}/track_shipments.py" "$@"

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[botantony]

Hello @anir0y. This looks like a nice piece of software, but it currently does not meet the notability requirements for inclusion into Homebrew-core: https://docs.brew.sh/Acceptable-Formulae#niche-or-self-submitted-stuff

For now you can create and maintain your own tap:

• https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap
• https://brew.sh/2020/11/18/homebrew-tap-with-bottles-uploaded-to-github-releases/

Once it becomes notable enough, we would love to see it in the Homebrew-core repository

[botantony]

Why this Python version and not the latest?

[botantony]

Suggested change

(bin/"unified-courier-tracker").chmod 0o755

[botantony]

Homebrew requires a simple test that checks if a program can do basic stuff correctly. From Formula Cookbook:

We want tests that don’t require any user input and test the basic functionality of the application. For example foo build-foo input.foo is a good test and (despite their widespread use) foo --version and foo --help are bad tests. However, a bad test is better than no test at all.

[bevanjkay]

Closing this for now due to the notability requirements.