-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ocpn-install: Cannot parse plugin name from tarball name #60
Comments
It's good this is happening now, as it will be a little disruptive to creating good catalogs. I assume "tarball name" is the 'tarball-URL'. Quite frankly, I have seen many 'tarball-URL' that do not match the "CommonName" as they are changed, fixed and doctored throughout the Frontend process (both frontends). I am just saying that by using 'tarball-URL' we will really have to clean it all up so that it matches "CommonName" and that will take some time and effort. I hope we can nail this down. |
From Tarball Names
In this case I know that the CommonName is actually "WeatherFax".
Is there any reason this can't be shortened somewhat? |
The actual quote is Which means that weatherfax_pi-1.9.4.1-ov50-1.16_darwin-10.13.6-macos.tar.gz will be parsed as Everything here is just fine besides target-os-version which should be 10.13.6 (drop the -macos suffix, it duplicates the darwin part) EDIT: Note that the common name stuff is dropped, it will not be possible to force plugins to use the common name as the name in the tarball. We are leaving this as it is, using the established name typically with a _pi suffix. |
Thanks. So the Tarball Name is at the "end" and should be: What are the "Beginning" and "Midddle" parts of the Target-URL? |
Currently, ocpn-install parses the plugin from tarball name, using a simple heuristic the any plugins called name_pi has a plugin name (common name name.
This heuristic does not hold. The only reliable way to get the filename is from the xml metadata. See discussion in bdbcat/oesenc_pi#79
The text was updated successfully, but these errors were encountered: