Just the .wepm file, and the only thing I changed was making the first letter of each word a capital. When downloading a package from script central, the package name, including capitalization seems to stay the same; However, when downloading with the install packages script, all of the letters seem to be changed to small letters. This seems to make no difference to the end user, but when I went to update a package, I used one which had been downloaded with the install packages script, and I was unable to update the package. I finally deleted the package, and created a new one which was successful. So, I just need to take a little more care to keep my original packages separate from packages that I download with install packages. Jeff Weiss
-----Original Message----- From: Chip Orange [mailto:[email protected]] Sent: Tuesday, October 26, 2010 7:33 PM To: [email protected] Subject: RE: re-naming script packages Jeff, what exactly are you renaming? is it just the .wepm file, or are you renaming the .vbs file, or perhaps the entry in the wineyes.ini file? what's being changed? (it's my thought that changing the case of the .wepm file has no effect, but almost anything else does have one). Chip ________________________________ From: Jeff Weiss [mailto:[email protected]] Sent: Tuesday, October 26, 2010 12:03 PM To: [email protected] Subject: re-naming script packages I would like to ask Aaron and others if there is any reason not to rename script packages? As you know, when you download a script package, at least with Jamal's script, the package name is all in small letters. I often rename my script packages, starting each word with a capital so that it sounds better. Is there a reason not to do this? The reason I ask, when I went to update my TextToClip package, it would not update the version number correctly. Even though I entered 1.4 in the script package, and I had 1.4 in the xml file, it kept showing 1.3. I ended up deleting the package, and creating en entirely new package and now all of the info is correct. I just don't understand why I couldn't update a package which had been renamed by me. Any suggestions or explanations would be appreciated. Thanks, Jeff Weiss
