31 May
2007
31 May
'07
10:02 p.m.
Lukas Renggli a écrit :
| > | > I found that the PUSecurity instances maintain the Settings in the
| > | > arrays
| > | > #ownerPermissions and #groupPermissions. How can I remove them
| > in each
| > | > decorations ?
| > |
| > | Did you try something like?
| > |
| > | PUSecurity allInstancesDo: [ :e | e remove ]
| >
| > That's what I just was doing. Unfortunately it's the only way for
| > instance.
|
| That would be preserve all the security settings ...
|
| PUSecurity allInstancesDo: [ :e |
| e ownerPermissions: (e ownerPermissions
| reject: [ :f | f command isObsolete ]).
| e groupPermissions: (e groupPermissions
| reject: [ :f | f command isObsolete ]).
| e otherPermissions: (e otherPermissions
| reject: [ :f | f command isObsolete ]).
|
That works.
I was searching a thing like that. One must add a "f command isNil" to
filter all bad built PUPermission. Maybe it would be cool to add such a
test for each Pier upgrade. I did this:
(PUSecurity instVarNames
select: [:p | '*Permissions' match: p])
do: [:me | PUSecurity allInstancesDo: [:ea |
ea perform: (me , ':') asSymbol
with: ((ea perform: me asSymbol) reject:
[:c | c command isNil or:
[c command isObsolete]])]].
Thanks,
--
Martial
| Lukas
|
| --
| Lukas Renggli
| http://www.lukas-renggli.ch
|
|
|
| _______________________________________________
| SmallWiki, Magritte, Pier and Related Tools ...
| https://www.iam.unibe.ch/mailman/listinfo/smallwiki