[Pharo-project] looking for the description of the MC file package format convention
Hi guys I know that somewhere we have this convention written and I would like to find it. PackageName-author.number[(branch)].mcz Stef
On Jan 24, 2013, at 11:54 AM, Stéphane Ducasse wrote:
Hi guys
I know that somewhere we have this convention written and I would like to find it.
PackageName-author.number[(branch)].mcz
I found <hyphenated-package-name>.<dotted.branch.tag>-<initials>.<count>.mcz there http://lists.squeakfoundation.org/pipermail/seaside-dev/2011-February/004558... Is it correct? Stef
Stef, That looks correct. Dale ----- Original Message ----- | From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> | To: Pharo-project@lists.gforge.inria.fr | Sent: Thursday, January 24, 2013 6:57:57 AM | Subject: Re: [Pharo-project] looking for the description of the MC file package format convention | | | On Jan 24, 2013, at 11:54 AM, Stéphane Ducasse wrote: | | > Hi guys | > | > I know that somewhere we have this convention written and I would | > like to find it. | > | > PackageName-author.number[(branch)].mcz | > | | I found | <hyphenated-package-name>.<dotted.branch.tag>-<initials>.<count>.mcz | | there | http://lists.squeakfoundation.org/pipermail/seaside-dev/2011-February/004558... | | Is it correct? | | Stef
Ok then one of these days I will introduce a MCName like in Squeak. Stef
Stef,
That looks correct.
Dale
----- Original Message ----- | From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> | To: Pharo-project@lists.gforge.inria.fr | Sent: Thursday, January 24, 2013 6:57:57 AM | Subject: Re: [Pharo-project] looking for the description of the MC file package format convention | | | On Jan 24, 2013, at 11:54 AM, Stéphane Ducasse wrote: | | > Hi guys | > | > I know that somewhere we have this convention written and I would | > like to find it. | > | > PackageName-author.number[(branch)].mcz | > | | I found | <hyphenated-package-name>.<dotted.branch.tag>-<initials>.<count>.mcz | | there | http://lists.squeakfoundation.org/pipermail/seaside-dev/2011-February/004558... | | Is it correct? | | Stef
I found GoferVersionReference>>parseName: aString | basicName | basicName := aString last isDigit ifTrue: [ aString ] ifFalse: [ (aString copyUpToLast: $.) copyUpTo: $( ]. package := basicName copyUpToLast: $-. (package includes: $.) ifFalse: [ branch := '' ] ifTrue: [ branch := package copyAfter: $.. package := package copyUpTo: $. ]. author := (basicName copyAfterLast: $-) copyUpToLast: $.. versionNumber := (basicName copyAfterLast: $-) copyAfterLast: $.. (versionNumber notEmpty and: [ versionNumber allSatisfy: [ :each | each isDigit ] ]) ifTrue: [ versionNumber := versionNumber asInteger ] ifFalse: [ versionNumber := 0 ] Now I do not get why we have copyUpTo: $( may be some files have ( ) Does anybody remember? Stef
Stef, Over the years I have seen all kinds of weird junk in mcz file names, including a number with embedded $(. Presumably that code was put in in self defense against a poorly formed file name in one of the repositories that Lukas was using:) Dale ----- Original Message ----- | From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> | To: Pharo-project@lists.gforge.inria.fr | Sent: Thursday, January 24, 2013 7:03:00 AM | Subject: Re: [Pharo-project] looking for the description of the MC file package format convention | | I found | | GoferVersionReference>>parseName: aString | | basicName | | basicName := aString last isDigit | ifTrue: [ aString ] | ifFalse: [ (aString copyUpToLast: $.) copyUpTo: $( ]. | package := basicName copyUpToLast: $-. | (package includes: $.) | ifFalse: [ branch := '' ] | ifTrue: [ | branch := package copyAfter: $.. | package := package copyUpTo: $. ]. | author := (basicName copyAfterLast: $-) copyUpToLast: $.. | versionNumber := (basicName copyAfterLast: $-) copyAfterLast: $.. | (versionNumber notEmpty and: [ versionNumber allSatisfy: [ :each | | each isDigit ] ]) | ifTrue: [ versionNumber := versionNumber asInteger ] | ifFalse: [ versionNumber := 0 ] | | Now I do not get why we have copyUpTo: $( | may be some files have ( ) | | Does anybody remember? | | Stef
Yes I thought about that too :) On Jan 24, 2013, at 2:04 PM, Dale Henrichs wrote:
Stef,
Over the years I have seen all kinds of weird junk in mcz file names, including a number with embedded $(.
Presumably that code was put in in self defense against a poorly formed file name in one of the repositories that Lukas was using:)
Dale
----- Original Message ----- | From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> | To: Pharo-project@lists.gforge.inria.fr | Sent: Thursday, January 24, 2013 7:03:00 AM | Subject: Re: [Pharo-project] looking for the description of the MC file package format convention | | I found | | GoferVersionReference>>parseName: aString | | basicName | | basicName := aString last isDigit | ifTrue: [ aString ] | ifFalse: [ (aString copyUpToLast: $.) copyUpTo: $( ]. | package := basicName copyUpToLast: $-. | (package includes: $.) | ifFalse: [ branch := '' ] | ifTrue: [ | branch := package copyAfter: $.. | package := package copyUpTo: $. ]. | author := (basicName copyAfterLast: $-) copyUpToLast: $.. | versionNumber := (basicName copyAfterLast: $-) copyAfterLast: $.. | (versionNumber notEmpty and: [ versionNumber allSatisfy: [ :each | | each isDigit ] ]) | ifTrue: [ versionNumber := versionNumber asInteger ] | ifFalse: [ versionNumber := 0 ] | | Now I do not get why we have copyUpTo: $( | may be some files have ( ) | | Does anybody remember? | | Stef
participants (2)
-
Dale Henrichs -
Stéphane Ducasse