[Squeak 4.0] Anyone know much about the format of the sources/changes files?

>
>>>>>> "Ronald" == Ronald Spengler <[hidden email]> writes:
>
> Ronald> Good people of Squeak,
> Ronald> We need to have a license statement at the top of our sources file for
> Ronald> the 4.0 release. I've been futsing with it without success.
>
> Ronald> I've tried:
>
> Ronald> 'foo'!
> Ronald> 'foo'!!
> Ronald> !'foo'!
>
> (I think) The sources file is always accessed according to byte offsets.  Look
> at the code for #condenseSources, and make sure the first thing it does is
> write the license before rewriting everything else.

> On 25.02.2010, at 02:38, Randal L. Schwartz wrote:
>>
>>>>>>> "Ronald" == Ronald Spengler <[hidden email]> writes:
>>
>> Ronald> Good people of Squeak,
>> Ronald> We need to have a license statement at the top of our sources file for
>> Ronald> the 4.0 release. I've been futsing with it without success.
>>
>> Ronald> I've tried:
>>
>> Ronald> 'foo'!
>> Ronald> 'foo'!!
>> Ronald> !'foo'!
>>
>> (I think) The sources file is always accessed according to byte offsets.  Look
>> at the code for #condenseSources, and make sure the first thing it does is
>> write the license before rewriting everything else.
>
> Randal is right. You can not just add something at the beginning of the sources or changes file. These are *NOT* text files but databases, the offsets are held in the image (each method knows the file position of its source code). The normal way to put a license in the beginning would be via #condenseSources - which we need to do anyway to purge all older versions of methods.
>
> - Bert -
>
>
>
>

> On 25.02.2010, at 10:42, Enrico Schwass wrote:
>>
>> Alexander Lazarević <[hidden email]> writes:
>>
>>> Btw, is there something speaking against #condenseSources asking for
>>> the destination of the new sources file? At least on unix like systems
>>> the assumption, that the sources file encompass the vm file in the
>>> same directory (e.g. /usr/bin) is most likely wrong.
>>
>> +1
>
> Or simply create it in FileDirectory default.
>
> - Bert -
>
>
>

>
> Bert Freudenberg wrote:
>> Randal is right. You can not just add something at the beginning of
>> the sources or changes file. These are *NOT* text files but
>> databases, the offsets are held in the image (each method knows the
>> file position of its source code).
>
> So, just as an aside, over an idle couple of days this week I
> implemented the Git repository format in Smalltalk. (This is why I was
> asking about the SystemChangeNotifier earlier.)
>
> http://www.squeaksource.com/Git.html
>
> So far, it can
>
> - initialize repositories
> - read and write loose objects (blobs, trees, commits, tags)
> - read packed objects (but not write them, yet)
> - resolve and update refs (tags and branch heads)

> On 25.02.2010, at 02:38, Randal L. Schwartz wrote:
>>
>>>>>>> "Ronald" == Ronald Spengler <[hidden email]> writes:
>>
>> Ronald> Good people of Squeak,
>> Ronald> We need to have a license statement at the top of our sources file for
>> Ronald> the 4.0 release. I've been futsing with it without success.
>>
>> Ronald> I've tried:
>>
>> Ronald> 'foo'!
>> Ronald> 'foo'!!
>> Ronald> !'foo'!
>>
>> (I think) The sources file is always accessed according to byte offsets.  Look
>> at the code for #condenseSources, and make sure the first thing it does is
>> write the license before rewriting everything else.
>
> Randal is right. You can not just add something at the beginning of the sources or changes file. These are *NOT* text files but databases, the offsets are held in the image (each method knows the file position of its source code). The normal way to put a license in the beginning would be via #condenseSources - which we need to do anyway to purge all older versions of methods.
>
> - Bert -
>
>
>
>

> I have a change in place for condenseSources   My question was really
> about how to put the license at the top in a way that can be written.
>
> I want to be sure though, is there a particular method which should be
> called within condenseSources to add comment text to the top?
>
> My (perhaps naive) implementation is doing something like:
>
> f nextPutall: license
>
> On Thursday, February 25, 2010, Bert Freudenberg <[hidden email]> wrote:
>> On 25.02.2010, at 02:38, Randal L. Schwartz wrote:
>>>>>>>> "Ronald" == Ronald Spengler <[hidden email]> writes:
>>> Ronald> Good people of Squeak,
>>> Ronald> We need to have a license statement at the top of our sources file for
>>> Ronald> the 4.0 release. I've been futsing with it without success.
>>>
>>> Ronald> I've tried:
>>>
>>> Ronald> 'foo'!
>>> Ronald> 'foo'!!
>>> Ronald> !'foo'!
>>>
>>> (I think) The sources file is always accessed according to byte offsets.  Look
>>> at the code for #condenseSources, and make sure the first thing it does is
>>> write the license before rewriting everything else.
>> Randal is right. You can not just add something at the beginning of the sources or changes file. These are *NOT* text files but databases, the offsets are held in the image (each method knows the file position of its source code). The normal way to put a license in the beginning would be via #condenseSources - which we need to do anyway to purge all older versions of methods.
>>
>> - Bert -
>>
>>
>>
>>
>

> And is
>
> self setMacFileInfoOn: SmalltalkImage current changesName.
> self setMacFileInfoOn: SmalltalkImage current sourcesName.
>
> still necessary??
>
> Alex
>
> On Thu, Feb 25, 2010 at 10:49, Bert Freudenberg <[hidden email]> wrote:
>> On 25.02.2010, at 10:42, Enrico Schwass wrote:
>>>
>>> Alexander Lazarević <[hidden email]> writes:
>>>
>>>> Btw, is there something speaking against #condenseSources asking for
>>>> the destination of the new sources file? At least on unix like systems
>>>> the assumption, that the sources file encompass the vm file in the
>>>> same directory (e.g. /usr/bin) is most likely wrong.
>>>
>>> +1
>>
>> Or simply create it in FileDirectory default.
>>
>> - Bert -
>>
>>
>>
>

> I did a quick test, and I think this should work:
>
>         license := 'Put your license text here'.
>         stream nextChunkPut: license storeString.
>         ".... Continue with condense changes ...."
>
> What it does is storing the license as a string literal (#storeString) so that the sources file will begin with the license as string and consequently the license can be read back in and parsed via:
>
>         license := Compiler evaluate: ((Smalltalk sourcesFile) position: 0; nextChunk).
>
> If you didn't use storeString you might have problems with utilities that try to parse the sources file, i.e., ChangeList and friends.
>
> Cheers,
>   - Andreas
>
> Ronald Spengler wrote:
>
> I have a change in place for condenseSources   My question was really
> about how to put the license at the top in a way that can be written.
>
> I want to be sure though, is there a particular method which should be
> called within condenseSources to add comment text to the top?
>
> My (perhaps naive) implementation is doing something like:
>
> f nextPutall: license
>
> On Thursday, February 25, 2010, Bert Freudenberg <[hidden email]> wrote:
>
> On 25.02.2010, at 02:38, Randal L. Schwartz wrote:
>
> "Ronald" == Ronald Spengler <[hidden email]> writes:
>
> Ronald> Good people of Squeak,
> Ronald> We need to have a license statement at the top of our sources file for
> Ronald> the 4.0 release. I've been futsing with it without success.
>
> Ronald> I've tried:
>
> Ronald> 'foo'!
> Ronald> 'foo'!!
> Ronald> !'foo'!
>
> (I think) The sources file is always accessed according to byte offsets.  Look
> at the code for #condenseSources, and make sure the first thing it does is
> write the license before rewriting everything else.
>
> Randal is right. You can not just add something at the beginning of the sources or changes file. These are *NOT* text files but databases, the offsets are held in the image (each method knows the file position of its source code). The normal way to put a license in the beginning would be via #condenseSources - which we need to do anyway to purge all older versions of methods.
>
> - Bert -
>
>
>
>
>
>
>
>
>
>

> At least I was close:)
>
> I will make the change to use #nextChunkPut: and #storeString. Thanks
> for all your help, Squeakers!
>
> On Thursday, February 25, 2010, Andreas Raab <[hidden email]> wrote:
>> I did a quick test, and I think this should work:
>>
>>         license := 'Put your license text here'.
>>         stream nextChunkPut: license storeString.
>>         ".... Continue with condense changes ...."
>>
>> What it does is storing the license as a string literal (#storeString) so that the sources file will begin with the license as string and consequently the license can be read back in and parsed via:
>>
>>         license := Compiler evaluate: ((Smalltalk sourcesFile) position: 0; nextChunk).
>>
>> If you didn't use storeString you might have problems with utilities that try to parse the sources file, i.e., ChangeList and friends.
>>
>> Cheers,
>>   - Andreas
>>
>> Ronald Spengler wrote:
>>
>> I have a change in place for condenseSources   My question was really
>> about how to put the license at the top in a way that can be written.
>>
>> I want to be sure though, is there a particular method which should be
>> called within condenseSources to add comment text to the top?
>>
>> My (perhaps naive) implementation is doing something like:
>>
>> f nextPutall: license
>>
>> On Thursday, February 25, 2010, Bert Freudenberg <[hidden email]> wrote:
>>
>> On 25.02.2010, at 02:38, Randal L. Schwartz wrote:
>>
>> "Ronald" == Ronald Spengler <[hidden email]> writes:
>>
>> Ronald> Good people of Squeak,
>> Ronald> We need to have a license statement at the top of our sources file for
>> Ronald> the 4.0 release. I've been futsing with it without success.
>>
>> Ronald> I've tried:
>>
>> Ronald> 'foo'!
>> Ronald> 'foo'!!
>> Ronald> !'foo'!
>>
>> (I think) The sources file is always accessed according to byte offsets.  Look
>> at the code for #condenseSources, and make sure the first thing it does is
>> write the license before rewriting everything else.
>>
>> Randal is right. You can not just add something at the beginning of the sources or changes file. These are *NOT* text files but databases, the offsets are held in the image (each method knows the file position of its source code). The normal way to put a license in the beginning would be via #condenseSources - which we need to do anyway to purge all older versions of methods.
>>
>> - Bert -
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> --
> Ron
>

> On 25.02.2010, at 11:08, Tony Garnock-Jones wrote:
>>
>> Bert Freudenberg wrote:
>>> Randal is right. You can not just add something at the beginning of
>>> the sources or changes file. These are *NOT* text files but
>>> databases, the offsets are held in the image (each method knows the
>>> file position of its source code).
>>
>> So, just as an aside, over an idle couple of days this week I
>> implemented the Git repository format in Smalltalk. (This is why I was
>> asking about the SystemChangeNotifier earlier.)
>>
>> http://www.squeaksource.com/Git.html
>>
>> So far, it can
>>
>> - initialize repositories
>> - read and write loose objects (blobs, trees, commits, tags)
>> - read packed objects (but not write them, yet)
>> - resolve and update refs (tags and branch heads)
>
> Awesome!
>
>> I remember hearing something about a bit of good refactoring recently
>> that permitted *switching out the sources implementation* for an image.
>> Perhaps it could be backed onto a Git repository using this code.
>> Methods would then know the sha1 of the blob that holds the source.
>
> That might work indeed.
>
> However, the method source pointer is not only used for accessing the current code, but previous versions of the method too. So you would need some more info than just the blob.
>
>> #condenseSources feels very much like "git pack-objects" or "git gc".
>
> Not quite, #condenseSources is destructive. It's rather more like pruning history - it deletes all previous versions. With something like git we might never have to do that again. Yay!
>
>> I haven't done the network protocol yet (in large part because I can't
>> yet build (good) packs) so shelling out to "git fetch" and "git push" is
>> still needed for that.
>
> Do you have ideas yet for how to map the Smalltalk structure to file names? Possibly you could reuse the mapping from SqueakSVN
> http://www.hpi.uni-potsdam.de/hirschfeld/projects/squeaksvn/
>
> - Bert -
>
>
>
>