[Bug 284429] devel/android-tools: Rename fastboot to prevent conflict within $PATH

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 28 Jan 2025 23:00:10 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284429

            Bug ID: 284429
           Summary: devel/android-tools: Rename fastboot to prevent
                    conflict within $PATH
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: nc@FreeBSD.org
          Reporter: polarian@polarian.dev
             Flags: maintainer-feedback?(nc@FreeBSD.org)
          Assignee: nc@FreeBSD.org

Hello,

I would like to open discussions on solutions to fixing the $PATH issue with
fastboot.

FreeBSD ships with a fastboot within /sbin/fastboot which will take priority
over the android fastboot which is installed to /usr/local/bin/fastboot.

This has a few issues:

1. "flash-all.sh", the bundled flashing script in android ROMs will always call
FreeBSD's fastboot, which is bad.
2. Its a pain to have to type the full path

So I suggest installing it as android-fastboot, or afastboot for faster typing
so that this $PATH conflict doesn't occur. flash-all.sh already needs to be
modified to use the full path anyways, so it already breaks flashing without
modification, so this change is breaking something which is already broken.

Sure you can always add an alias to your shrc, but I do not feel like that is a
concrete solution to the problem.

Obviously this is a short term quality of life improvement, does anyone else
have any better ideas which allows flash-all.sh to work seamlessly without
modification?

I think the real benefit is if ROM bundles started shipping with a uname check
and hard code the path into it, but Google won't care about that, too much
effort for such a small community of hackers (which are fully capable of fixing
the script themself).

Adjusting the $PATH is likely not wise either, although would fix this problem.

Thank you,
Polarian

-- 
You are receiving this mail because:
You are the assignee for the bug.