Then we could run the decoder with no arguments, and it would find the installed operating config files (as shown in the run below). $ sudo adobe-licensing-toolkit -p -i -f online-default-allapps/ngl-preconditioning-data.json If you have some other directory that you want it to look in for license files (for example, if your customer zipped up their OperatingConfigs directory and sent the zip to you), just name that directory on the command line, as in: If invoked without any command-line arguments, the adobe-license-decoder will look for a globally installed OperatingConfigs directory, and decode all the license files found in that directory. It can then be invoked as adobe-license-decoder from any command line (examples below). So to install it on a given machine, just download the appropriate Mac or Win binary from the latest release page, rename it without the platform suffix (to adobe-license-decoder or adobe-license-decoder.exe), and put it somewhere in your command-line search path. The adobe-license-decoder is a command line tool that doesn't require any special privileges. It's like a "secret decoder ring" for the licenses! Installation This tool can examine globally-installed SDL and FRL license files and tell you which apps they are for, which packages they are from, when they were installed, when they expire, and so on. While this information is invaluable, it's specific to the user account it is run in, and it doesn't give any general information about the licenses that are installed on the machine that haven't been used.Įnter the adobe-license-decoder, a different command-line tool that can tell you about FRL and SDL license files both before and after installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |