On Linux, we've been making use of the preview "executable images" support (from preview/bin), and it works really well for us. One thing that's annoying, however, is that if we startup an image and do a Save Image As..., the new image does not have execute permission turned on like the source image did.
How hard would it be to make the new image have the same permissions as the old? Thanks, Randy -- Randy Coulman [hidden email] _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hi Randy,
I've been thinking the same thing, created AR#57286 for this. Martin "Randy Coulman"<[hidden email]> wrote: > On Linux, we've been making use of the preview "executable images" support > (from preview/bin), and it works really well for us. One thing that's > annoying, however, is that if we startup an image and do a Save Image As..., > the new image does not have execute permission turned on like the source > image did. > > How hard would it be to make the new image have the same permissions as the > old? > > Thanks, > Randy > -- > Randy Coulman > [hidden email] > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Having this solved in the future is good. And here is a proposal for how
to solve it now. A solution depends on the VisualWorks version you are using. For VW75/76 the easiest way is adding a system event dependency. File in the attached code. This adds a method #setUnixXbitAfterSnapshot to SystemEventInterest class. The method's pragma installs a dependency on #finishedSnapshot, the event that is triggered whenever a snapshot has finished. Hope that helps Holger Guhl -- Senior Consultant * Certified Scrum Master * [hidden email] Tel: +49 231 9 75 99 21 * Fax: +49 231 9 75 99 20 Georg Heeg eK Dortmund Handelsregister: Amtsgericht Dortmund A 12812 [hidden email] schrieb: > Hi Randy, > > I've been thinking the same thing, created AR#57286 for this. > > Martin > > "Randy Coulman"<[hidden email]> wrote: > >> On Linux, we've been making use of the preview "executable images" support >> (from preview/bin), and it works really well for us. One thing that's >> annoying, however, is that if we startup an image and do a Save Image As..., >> the new image does not have execute permission turned on like the source >> image did. >> >> How hard would it be to make the new image have the same permissions as the >> old? >> >> Thanks, >> Randy >> -- >> Randy Coulman >> [hidden email] >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> >> > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > <?xml version="1.0"?> <st-source> <time-stamp>From VisualWorks®, 7.5 of 16. April 2007 on 26. Mai 2009 at 11:23:37</time-stamp> <methods> <class-id>Core.SystemEventInterest class</class-id> <category>dependencies-pragma</category> <body package="Tools-Dialogs" selector="setUnixXbitAfterSnapshot">setUnixXbitAfterSnapshot "On Unix, we like to change the file execution bit of the image file after saving the file such that the executability bit is on." <triggerAtSystemEvent: #finishedSnapshot> | imageFile | imageFile := (ObjectMemory imagePrefix , '.im') asFilename. OSHandle currentOS == #unix ifTrue: [imageFile setProtection: 8r755]</body> </methods> </st-source> _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |