Posted on 07-09-2010 09:08 AM
Hello all,
Casper Hates Apostrophes in Package Names. I encountered this a long time ago, but I forgot and it bit me again. Ever forget? Happened to me.
Composer allow you create a package and use an apostrophe in its file name, and
Casper Admin allows you to add a package which has an apostrophe in its file name. But when it comes time to send that package to a computer with Casper Remote (or, presumably, with a policy, or during imaging), the apostrophe causes problems with the CLI tools Casper employs, and that package is not installed.
So, my feature request is this:
1) Enable Composer to detect and reject apostrophes in package names; i.e., prevent the operator from naming a package iPhoto - iLife '09.
2) Enable Casper Admin t detect and reject apostrophes in package names; i.e., prevent the operator from adding a package named iPhoto - iLife '09.
Please, save me from myself!
--
Bryan Vines
bkvines at wgclawfirm.com
Posted on 07-09-2010 10:53 AM
That really helps, thank you! We were puzzled as to why iLife '09 wouldn't
install until we re-created the package (and just happened to name it
iLife09).
Tatian
Posted on 07-12-2010 03:33 AM
I had the same issuer Friday.. this would be very helpful!
Ben Toms
IT Support Analyst GREY Group
The Johnson Building, 77 Hatton Garden, London, EC1N 8JS
T: +44 (0) 20-3037-3819 |
Main: +44 (0) 20 3037 3000 | IT Helpdesk: +44 (0) 20 3037 3883