-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/13/2010 3:25 PM, [email protected] wrote: > Hi Ethan, > Just a different idea below. > Thank you, > Clay > > On Mon, 12 Jul 2010, Ethan Quach wrote: > > [snip...] >> I looked into this, and the name of the file as hosted by the install >> server >> is not even known to manifest-locator service. The file is >> ascertained via >> a POST request and hence the client never has a handle to the file name >> as it lives on the server. If we want to record this name in the >> install_log, >> we need to make changes to accommodate this. Since this applies to >> today's manifest XML file as well, I would like to keep this issue >> separate >> from this design if that's okay with you. > > We actually have the file name. The manifest name, today, comes from the > AI manifest's name attribute from the ai_manifest tag. So the client > does know what the manifest's name was if it looks at that attribute in > the downloaded manifest.
Reading through this, it occurred to me that even if the name was known the path (I'm assuming the name would be the full path to the script) would be where ever the install service had squirreled it away when it was added on the server. I doubt that is really that useful. What the user really wants is the location the file lived in when it was originally added. The manifest name attribute listed above is a little more useful to identify which manifest was selected, but will only be present when a true manifest is located, and not in a script. Also you'd have to search through your manifest sources with grep to find the same one. It also occurred to me that many enterprises will want to use source code control on these scripts (and manifests) to track who made which changes and when, and likely they will embed pathname, filename, and version information into the manifests and scripts themselves. If you really want to be able to easily log this info about the script or manifest that was selected, then dedicating an attribute (for the manifest) or an easily searched for comment format (for the scripts) would allow you log that info, and show the user exactly where to locate the source for the file in question. After thinking all this through though, I'm not sure this needs to be logged. Any one using source control (or even those not using it) will likely embed this info in comments in the manifests and scripts anyway, and the current proposal makes those files available, so instead of looking in the logs for this info, the user would just have to look in the files themselves. Just thinking out loud here.... ;) -Kyle > > [snip...] > _______________________________________________ > caiman-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) iQEcBAEBAgAGBQJMPMeSAAoJEEADRM+bKN5w+0cIAJJT294+N8k805Fg2zoIv9IX dvNoaGs/o0I7RlrVLGeVQ7nkOuX5uVC25ysVGHCH1U+9cgyD5vwr7aavpzaKFkdL 89RRgx/JsRkzHDuEMPKOcWmgGTELGKB9Ap67zuweIQMubKAErw2FM6hG5RhSEURp juRxGCUyDlcWl5ZkHo9VAvgbzPg0qNBmCo1m7pLva2otqhVSeFpxFcEMGuAm4JN2 6XDKMFBbAowRj8Q9SaiPn0bqx6Wul4HKYpvL+Mkqq+CIoVaVBmFxWHxCd6ESzCan 4Jov5vq4n0WyO4ceVxzikW1Vofytrvj9VgDftRdQFAg5MLTzHHOKT6cFccCZVlA= =QiyK -----END PGP SIGNATURE----- _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
