Am 21.07.2013 um 10:16 schrieb Marcus Denker <[email protected]>:
> > On Jul 21, 2013, at 10:05 AM, Damien Cassou <[email protected]> wrote: > >> Hi, >> >> in SmalltalkImage>>checkAndOpenSourcesAndChanges, there is some code >> that looks like this: >> >> [...] >> changes isReadOnly >> ifTrue: [ self inform: 'Pharo cannot write to the >> changes file ...' ]. >> [...] >> >> This code raises a warning if the changes file can't be written to. In >> the PharoLauncher case, the image and changes file won't be writable >> and it is ok (they will be in a place like /usr/lib). I certainly >> don't want my users to see this warning. >> >> What can I do please? >> > > We need to get rid of .changes and .sources… it will solve all kinds of > problems. > What will be the replacement? Norbert
