1.1.3

macup 1.1.3

tiny lil update

Changes

• macup will now remind you to update the database if it's been more than two weeks since a refetch
• fix more module errors
• set up git and cleaned up repository
• the binary is much, much smaller now (ULTRAMINIFICATION)

Binaries

Prebuilt binaries are, as always, provided below, in /dist (once decompressed)

1.1.2

macup 1.1.2

can you believe i updated it twice today (even though this one is very small)

Changes

• Prefix arguments are no longer case-sensitive (E0:D5:33 is the same as e0:d5:33)
• You can now use -n to specify how many prefixes to return when using macup -r
• Tweaked help message...again
• Fixed issue with the binary where modules would appear uninstalled despite being compiled
• Other bugfixes idk

Binaries

Compiled binaries provided below. Once decompressed, the binary can be found in /dist

1.1.0

macup v1.1.0

despite how many times i told myself i didnt need to update it, i updated it

Changes

• Rewrote the whole tool in python because my bash implementation sucked. It is now a fully bundled python executable that (i think) can be run on any system with python3 installed, including windows (i think)
• Added the option to save the output of macup -v <vendor> to a specified .txt filename
• Removed my bad argument handling and replaced it with a real argument parser (argparse) so it's way more stable now
• Tweaked help message (macup -h) so that it looks more professional and official.
• Vendor matching is no longer case-sensitive and no longer strict-matches unnecessarily
• yes, it can still be run offline after the rewrite!
• macup -i now requires superuser permissions on Linux. It should not matter on windows.
• Arguments now have expanded counterparts for the weirdos out there (e.g. -v --> --vendor)
• Limited argument chaining now works, you can now run -v and -p in the same command (for whatever reason)
• Arguments are no longer positional
• Changed output format (<prefix> <vendor> --> <prefix> | <vendor)

Binaries

The compiled binary is provided below. Unfortunately the tarball is no longer 900 bytes, given that the modules are compiled into the binary. Feel free to let me know (open an issue) if there are any problems with it.

(The binary itself is located in /dist)