Hi I'm writing a configuration for Soup and it depends on XMLParser. Does the following really express that Soup is dependent from XMLSupport? <version: '1.0'> spec for: #pharo do: [ spec blessing: #baseline. spec repository: 'http://www.squeaksource.com/Soup'. spec project: 'XMLSupport' with: [ spec className: 'ConfigurationOfXMLSupport'; repository: 'http://www.squeaksource.com/XMLSupport' ; loads: #('Core' 'Tests'); file: 'ConfigurationOfXMLSupport'. ] ] I will use this example for the book after instead of A and B. Because I put in the chapter spec package: 'CoolToolSet-Core'; package: 'CoolToolSet-Tests' with: [ spec requires: #('CoolToolSet-Core') ]; And I was wondering if the requires: is implicit above. and if this is the for: do: that does it. Stef
|
Hi,
This is a default dependency, and so XMLSupport will be loaded if you load version '1.0' of Soup. However, the one thing you do not know is the order. If you do not specify which of the Soup packages depend on XMLSupport, you do not know when XMLSupport will be loaded. This is probably not a problem in this case, but it is best to be explicit about it (saves pain later on). Cheers, Doru On 30 Dec 2011, at 09:23, stephane ducasse wrote: > Hi > > I'm writing a configuration for Soup and it depends on XMLParser. > > Does the following really express that Soup is dependent from XMLSupport? > > > baseline10: spec > > <version: '1.0'> > spec for: #pharo do: [ > spec blessing: #baseline. > spec repository: 'http://www.squeaksource.com/Soup'. > > spec project: 'XMLSupport' > with: [ spec > className: 'ConfigurationOfXMLSupport'; > repository: 'http://www.squeaksource.com/XMLSupport' ; > loads: #('Core' 'Tests'); > file: 'ConfigurationOfXMLSupport'. > ] > ] > > > I will use this example for the book after instead of A and B. > > > > Because I put in the chapter > > <page46image13964.png> > spec > package: 'CoolToolSet-Core'; > package: 'CoolToolSet-Tests' with: [ spec requires: #('CoolToolSet-Core') ]; > > And I was wondering if the requires: is implicit above. and if this is the for: do: that does it. > > Stef -- www.tudorgirba.com "Every thing has its own flow." |
In reply to this post by stephane ducasse-2
On Fri, Dec 30, 2011 at 9:23 AM, stephane ducasse <[hidden email]> wrote:
Not really. At least not if that piece of code is the whole baseline10: method. The thing is that there is nobody (a package/s) from Soup that requires XMLSupport. Hence, XMLSupport (as it is right now) will ONLY be loaded if you load 'ALL' or if you load 'default' (if you didn't change the default value of 'default'). Imagine that you then create a group called Core and you put your core packages of Soup, and you say that the 'default' group is Core. In that case, XMLSupport won't be loaded. It will be loaded of course if you manually add it to the group. Conclusion: 99% of the times, if you put a project reference is because you have packages (from Soup in this case) that should require XMLSupport. Apart from that, there is the problem Tudor mentions, which is the order. Since there is no requires, it may happen that Soup will be loaded before XMLSupport, and hence, you wil have the nice Monticello popup saying that you need classes XXX.
-- Mariano http://marianopeck.wordpress.com |
On Dec 31, 2011, at 11:37 AM, Mariano Martinez Peck wrote: > > > On Fri, Dec 30, 2011 at 9:23 AM, stephane ducasse <[hidden email]> wrote: > Hi > > I'm writing a configuration for Soup and it depends on XMLParser. > > Does the following really express that Soup is dependent from XMLSupport? > > > > Not really. At least not if that piece of code is the whole baseline10: method. The thing is that there is nobody (a package/s) from Soup that requires XMLSupport. Hence, XMLSupport (as it is right now) will ONLY be loaded if you load 'ALL' or if you load 'default' (if you didn't change the default value of 'default'). Imagine that you then create a group called Core and you put your core packages of Soup, and you say that the 'default' group is Core. In that case, XMLSupport won't be loaded. It will be loaded of course if you manually add it to the group. > Conclusion: 99% of the times, if you put a project reference is because you have packages (from Soup in this case) that should require XMLSupport. Cool I'm the only guy with you trying to document metacello and I'm confused. It gives a lot of confidence. Pffff shit. I'm fed up this is too complex. Because I do not want to load with default, all or whatever. I think that metacello is getting too complex. I want to load stable so is stable loading All, default? I think that metacello grew organically and it needs a good revisit. baseline10: spec <version: '1.0-baseline'> spec for: #pharo do: [ spec blessing: #baseline. spec description: 'First Full Configuration'. spec author: 'StephaneDucasse'. spec timestamp: '29/12/2011 12:29'. spec repository: 'http://www.squeaksource.com/Soup'. spec package: 'Soup-Core'; package: 'Soup-Tests-Core' with: [spec requires: 'Soup-Core'] ; package: 'Soup-Help' with: [spec requires: 'Soup-Core']. spec project: 'XMLSupport' with: [ spec className: 'ConfigurationOfXMLSupport'; versionString: #stable; repository: 'http://www.squeaksource.com/XMLSupport'. ] ] If I must express dependencies to package of XMLSupport should I depend on Porject or packages inside these packages… (I have no idea how to express that). version10: spec <version: '1.0' imports: #('1.0-baseline')> spec for: #pharo do: [ spec blessing: #development. spec project: 'XMLSupport' with: '1.2.0'. spec package: 'Soup-Core' with: 'Soup-Core-sd.11'; package: 'Soup-Tests-Core' with: 'Soup-Tests-Core-sd.3'; package: 'Soup-Help' with: 'Soup-Help-StephaneDucasse.2' ]. > > Apart from that, there is the problem Tudor mentions, which is the order. Since there is no requires, it may happen that Soup will be loaded before XMLSupport, and hence, you wil have the nice Monticello popup saying that you need classes XXX. > > > > baseline10: spec > > <version: '1.0'> > spec for: #pharo do: [ > spec blessing: #baseline. > spec repository: 'http://www.squeaksource.com/Soup'. > > spec project: 'XMLSupport' > with: [ spec > className: 'ConfigurationOfXMLSupport'; > repository: 'http://www.squeaksource.com/XMLSupport' ; > loads: #('Core' 'Tests'); > file: 'ConfigurationOfXMLSupport'. > ] > ] > > > I will use this example for the book after instead of A and B. > > > > Because I put in the chapter > > <page46image13964.png> > spec > package: 'CoolToolSet-Core'; > package: 'CoolToolSet-Tests' with: [ spec requires: #('CoolToolSet-Core') ]; > > And I was wondering if the requires: is implicit above. and if this is the for: do: that does it. > > Stef > > > > -- > Mariano > http://marianopeck.wordpress.com > |
In reply to this post by Mariano Martinez Peck
So the project section is just to declare where to find the information.
Now the following does not work because I cannot depend on package in XML Support. I do not understand why baseline10: spec <version: '1.0-baseline'> spec for: #pharo do: [ spec blessing: #baseline. spec description: 'First Full Configuration'. spec author: 'StephaneDucasse'. spec timestamp: '29/12/2011 12:29'. spec repository: 'http://www.squeaksource.com/Soup'. spec package: 'Soup-Core' with: [spec "requires: 'XMLSupport'" requires: 'XML-Parser' ; requires: 'XML-Tests-Parser']; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ package: 'Soup-Tests-Core' with: [spec requires: 'Soup-Core'] ; package: 'Soup-Help' with: [spec requires: 'Soup-Core']. spec project: 'XMLSupport' with: [ spec className: 'ConfigurationOfXMLSupport'; versionString: #stable; repository: 'http://www.squeaksource.com/XMLSupport'. ] ] While the baseline of XMLSupport specifies the packages package: 'XML-Parser' and package: 'XML-Tests-Parser':( baseline120: spec <version: '1.2.0-baseline'> spec for: #common do: [ spec blessing: #baseline; repository: 'http://www.squeaksource.com/XMLSupport'. spec project: 'XML-Writer' with: [ spec className: 'ConfigurationOfXMLWriter'; repository: 'http://www.squeaksource.com/XMLWriter' ]; package: 'Collections-OrderPreservingDictionary' with: [ spec repository: 'http://www.squeaksource.com/OrderPreservingDict' ]; package: 'Collections-BitmapCharacterSet' with: [ spec repository: 'http://www.squeaksource.com/BitmapCharacterSet' ]; package: 'XML-Parser' ^^^^^^^^^^^^^^^^^ with: [ spec requires: #('XML-Writer' 'Collections-OrderPreservingDictionary' 'Collections-BitmapCharacterSet') ]; package: 'XML-Tests-Parser' with: [ spec requires: 'XML-Parser' ]. spec package: 'Opax' with: [ spec repository: 'http://www.squeaksource.com/OPAX'; requires: 'XML-Parser' ]. spec group: 'default' with: #('Core'); group: 'Core' with: #('XML-Parser'); group: 'Tests' with: #('XML-Tests-Parser') ]. spec for: #squeakcommon do: [ spec package: 'Pastell' with: [ spec requires: #('XML-Parser'); repository: 'http://www.squeaksource.com/Pastell' ] ]. spec for: #gemstone do: [ spec repository: 'http://seaside.gemstone.com/ss/XMLSupport'. spec project: 'Grease Core' with: [ spec className: 'ConfigurationOfGrease'; versionString: '1.0.3-baseline'; loads: #('Core'); repository: 'http://www.squeaksource.com/MetacelloRepository' ]. spec package: 'Collections-OrderPreservingDictionary' with: [ spec file: 'Collections-OrderPreservingDictionary.g'; repository: 'http://seaside.gemstone.com/ss/PharoCompat']. spec package: 'SIXX' with: [ spec requires: #('XML-Parser' 'Grease Core'); repository: 'http://seaside.gemstone.com/ss/SIXX']. spec package: 'XML-Observable'. spec package: 'XML-Parser' with: [ spec file: 'XML-Parser.g']. spec group: 'Core' with: #('XML-Observable'); group: 'default' with: #('Core') ] |
In reply to this post by Mariano Martinez Peck
I have
ConfigurationOfXMLSupport>>baseline120: spec <version: '1.2.0-baseline'> spec for: #common do: [ spec blessing: #baseline; repository: 'http://www.squeaksource.com/XMLSupport'. spec project: 'XML-Writer' with: [ spec className: 'ConfigurationOfXMLWriter'; repository: 'http://www.squeaksource.com/XMLWriter' ]; package: 'Collections-OrderPreservingDictionary' with: [ spec repository: 'http://www.squeaksource.com/OrderPreservingDict' ]; package: 'Collections-BitmapCharacterSet' with: [ spec repository: 'http://www.squeaksource.com/BitmapCharacterSet' ]; package: 'XML-Parser' with: [ spec requires: #('XML-Writer' 'Collections-OrderPreservingDictionary' 'Collections-BitmapCharacterSet') ]; package: 'XML-Tests-Parser' with: [ spec requires: 'XML-Parser' ]. spec package: 'Opax' with: [ spec repository: 'http://www.squeaksource.com/OPAX'; requires: 'XML-Parser' ]. spec group: 'default' with: #('Core'); group: 'Core' with: #('XML-Parser'); group: 'Tests' with: #('XML-Tests-Parser') ]. Then I have ConifgurationOfSoup>>version10: spec <version: '1.0' imports: #('1.0-baseline')> spec for: #pharo do: [ spec blessing: #development. spec project: 'XMLSupport' with: '1.2.0'. spec package: 'Soup-Core' with: 'Soup-Core-sd.11'; package: 'Soup-Tests-Core' with: 'Soup-Tests-Core-sd.3'; package: 'Soup-Help' with: 'Soup-Help-StephaneDucasse.2' ]. baseline10: spec <version: '1.0-baseline'> spec for: #pharo do: [ spec blessing: #baseline. spec description: 'First Full Configuration'. spec author: 'StephaneDucasse'. spec timestamp: '29/12/2011 12:29'. spec repository: 'http://www.squeaksource.com/Soup'. spec package: 'Soup-Core' with: [spec requires: 'XMLSupport' ]; package: 'Soup-Tests-Core' with: [spec requires: 'Soup-Core'] ; package: 'Soup-Help' with: [spec requires: 'Soup-Core']. spec project: 'XMLSupport' with: [ spec className: 'ConfigurationOfXMLSupport'; versionString: #stable; repository: 'http://www.squeaksource.com/XMLSupport'. ] ] ConfigurationOfSoup>>version10: spec <version: '1.0' imports: #('1.0-baseline')> spec for: #pharo do: [ spec blessing: #development. spec project: 'XMLSupport' with: '1.2.0'. spec package: 'Soup-Core' with: 'Soup-Core-sd.11'; package: 'Soup-Tests-Core' with: 'Soup-Tests-Core-sd.3'; package: 'Soup-Help' with: 'Soup-Help-StephaneDucasse.2' ]. How can I say that I want to load the XML-Tests-Package? I guess that I cannot express dependencies to a package inside XMLSupport in a baseline because there is not enough information to find it package: 'Soup-Core' with: [spec requires: 'XMLSupport' ]; clearly identify XMLSupport project but package: 'Soup-Core' with: [spec requires: 'XML-Parser' ]; could be in two different projects So I tried version10: spec <version: '1.0' imports: #('1.0-baseline')> spec for: #pharo do: [ spec blessing: #development. spec project: 'XMLSupport' with: [spec loads: #('XML-Parser' 'XML-Tests-Parser'); versionString: '1.2.0']. spec package: 'Soup-Core' with: 'Soup-Core-sd.11'; package: 'Soup-Tests-Core' with: 'Soup-Tests-Core-sd.3'; package: 'Soup-Help' with: 'Soup-Help-StephaneDucasse.2' ]. Is it the way to do it? Because in the book we do not explain it. Stef |
In reply to this post by stephane ducasse-2
On Sat, Dec 31, 2011 at 12:34 PM, stephane ducasse <[hidden email]> wrote:
I am out of home now so a quickly answer: you are confusing two things: a) WHICH version to load. In that case, #stable is related to that. b) WHAT to load from an specific version (whatever version) a) and b) are totally independent. So #stable and ALL has nothing to do. With any version (whether it is stable or not) you can load what you want (ALL or something different) I think that metacello grew organically and it needs a good revisit. -- Mariano http://marianopeck.wordpress.com |
In reply to this post by stephane ducasse-2
On Sat, Dec 31, 2011 at 12:34 PM, stephane ducasse <[hidden email]> wrote:
"getting" ? Since when? there have been recent changes that make it more complex? As far as I can see fro your questions, most of them are from the beginning of Metacello. There weren't any significant change in Metacello in the last months. The only "big change" was several months ago with the introduction of symbolic versions. I want to load stable so is stable loading All, default? That's a very good question :) I found myself a couple of times in that situation. What I did in all those scenarios is to depend directly on the project. With #loads: you can say in which packages you depend, that is, which packages will be loaded. So for example, in this case, I would say that Soup-Core requires XMLSupport. And in the project reference to XMLSupport I will put a #loads: with what whatever Soup needs from XMLSupport. Then...it gets complicated when different packages of Soup require different packages of XMLSupport. I think here you can decide what to do. You can put all the required packages in the same project reference and then all your packages of Soup require the same project reference. Or...you can use #project:copyFrom: and create different project references to the same project and then make each Soup package to depend on each of them. Personally, I was never forced to this last scenario. In the contrary, I always did the first option.
-- Mariano http://marianopeck.wordpress.com |
In reply to this post by stephane ducasse-2
On Sat, Dec 31, 2011 at 12:45 PM, stephane ducasse <[hidden email]> wrote: So the project section is just to declare where to find the information.
No, you cannot do that because metacello won't find anything defined in the whole method as 'XML-Parser' or 'XML-Tests-Parser'. So...as I said in the previous email, you can depend directly in 'XMLSupport' and then you define: spec project: 'XMLSupport' with: [ spec className: 'ConfigurationOfXMLSupport'; versionString: #stable; loads: #( 'XML-Parser' 'XML-Tests-Parser' ) repository: 'http://www.squeaksource.com/XMLSupport'. ]
-- Mariano http://marianopeck.wordpress.com |
In reply to this post by stephane ducasse-2
On Sat, Dec 31, 2011 at 1:23 PM, stephane ducasse <[hidden email]> wrote: I have exactlly. Remember that with the builder received as an argument a kind of stack is created. And metacello won't find anything for those packages. And moreover, as you said, there could come from different projects. So I tried YES! -- Mariano http://marianopeck.wordpress.com |
On Sat, Dec 31, 2011 at 3:41 PM, Mariano Martinez Peck <[hidden email]> wrote:
No, wait. Almost ;) In the baseline you put: spec project: 'XMLSupport' with: [ spec className: 'ConfigurationOfXMLSupport'; versionString: #stable; loads: #( 'XML-Parser' 'XML-Tests-Parser' ); repository: 'http://www.squeaksource.com/XMLSupport'. ] and in the version you put: spec project: 'XMLSupport' with: '1.2.0'.
-- Mariano http://marianopeck.wordpress.com |
wait..what I say is that I do. But maybe what you showed also works, I don't know.
-- Mariano http://marianopeck.wordpress.com |
In reply to this post by Mariano Martinez Peck
>
> > > "getting" ? Since when? there have been recent changes that make it more complex? As far as I can see fro your questions, most of them are from the beginning of Metacello. There weren't any significant change in Metacello in the last months. The only "big change" was several months ago with the introduction of symbolic versions. the fact that nothing changes is ok but when I see time it takes me to describe precisely…. > I want to load stable so is stable loading All, default? > I think that metacello grew organically and it needs a good revisit. I would really like to extract the semantics and makes it simpler (even if less powerful). > > > > baseline10: spec > <version: '1.0-baseline'> > > spec for: #pharo do: [ > spec blessing: #baseline. > spec description: 'First Full Configuration'. > spec author: 'StephaneDucasse'. > spec timestamp: '29/12/2011 12:29'. > spec repository: 'http://www.squeaksource.com/Soup'. > > spec > package: 'Soup-Core'; > package: 'Soup-Tests-Core' with: [spec requires: 'Soup-Core'] ; > package: 'Soup-Help' with: [spec requires: 'Soup-Core']. > > spec project: 'XMLSupport' with: [ > spec className: 'ConfigurationOfXMLSupport'; > versionString: #stable; > repository: 'http://www.squeaksource.com/XMLSupport'. > ] > > ] > > If I must express dependencies to package of XMLSupport should I depend on Porject or packages inside these packages… (I have no idea how to express that). > > > That's a very good question :) I found myself a couple of times in that situation. What I did in all those scenarios is to depend directly on the project. With #loads: you can say in which packages you depend, that is, which packages will be loaded. So for example, in this case, I would say that Soup-Core requires XMLSupport. And in the project reference to XMLSupport I will put a #loads: with what whatever Soup needs from XMLSupport. Then...it gets complicated when different packages of Soup require different packages of XMLSupport. I think here you can decide what to do. You can put all the required packages in the same project reference and then all your packages of Soup require the same project reference. Or...you can use #project:copyFrom: and create different project references to the same project and then make each Soup package to depend on each of them. > Personally, I was never forced to this last scenario. In the contrary, I always did the first option. The point is that creating a lot of reference just to load the right packages is tedious. And I would like to explain that clearly with one single example. The coolBrowser and toolset Configuration is not sexy to me so that the reader gets an immediate shah effect. I tried and I should do another pass and add your next example. > > > > version10: spec > <version: '1.0' imports: #('1.0-baseline')> > > spec for: #pharo do: [ > spec blessing: #development. > spec project: 'XMLSupport' with: '1.2.0'. > > spec > package: 'Soup-Core' with: 'Soup-Core-sd.11'; > package: 'Soup-Tests-Core' with: 'Soup-Tests-Core-sd.3'; > package: 'Soup-Help' with: 'Soup-Help-StephaneDucasse.2' ]. > > > > > > > > > > Apart from that, there is the problem Tudor mentions, which is the order. Since there is no requires, it may happen that Soup will be loaded before XMLSupport, and hence, you wil have the nice Monticello popup saying that you need classes XXX. > > > > > > > > > > > > baseline10: spec > > > > <version: '1.0'> > > spec for: #pharo do: [ > > spec blessing: #baseline. > > spec repository: 'http://www.squeaksource.com/Soup'. > > > > spec project: 'XMLSupport' > > with: [ spec > > className: 'ConfigurationOfXMLSupport'; > > repository: 'http://www.squeaksource.com/XMLSupport' ; > > loads: #('Core' 'Tests'); > > file: 'ConfigurationOfXMLSupport'. > > ] > > ] > > > > > > I will use this example for the book after instead of A and B. > > > > > > > > Because I put in the chapter > > > > <page46image13964.png> > > spec > > package: 'CoolToolSet-Core'; > > package: 'CoolToolSet-Tests' with: [ spec requires: #('CoolToolSet-Core') ]; > > > > And I was wondering if the requires: is implicit above. and if this is the for: do: that does it. > > > > Stef > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > |
In reply to this post by Mariano Martinez Peck
>
Cool I will add it to the chapter because this is the other solution I did not cover.
> > > > No, you cannot do that because metacello won't find anything defined in the whole method as 'XML-Parser' or 'XML-Tests-Parser'. So...as I said in the previous email, you can depend directly in 'XMLSupport' and then you define: > > spec project: 'XMLSupport' with: [ > spec className: 'ConfigurationOfXMLSupport'; > versionString: #stable; > loads: #( 'XML-Parser' 'XML-Tests-Parser' ) > repository: 'http://www.squeaksource.com/XMLSupport'. > ] > |
In reply to this post by Mariano Martinez Peck
I'm writing both in the chapter because both work.
You can specify at the baseline and the version the loads: command. I just forgot that we could do it at the baseline and I thought that I had to create an extra reference. On Dec 31, 2011, at 3:43 PM, Mariano Martinez Peck wrote: > spec > project: 'XMLSupport' > with: '1.2.0'. > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > |
Stef and Mariano,
I've been on a 'real vacation' (i.e., not touching the computer for almost 10 days ... okay I touched the computer but just to read about basketball and movies ... okay I only fixed one Metacello bug in the first couple of days ... ) and haven't read my mail since before Xmas ... It looks like this discussion has been resolved, but if not let me know and I'll jump in ... Dale ----- Original Message ----- | From: "stephane ducasse" <[hidden email]> | To: "Mariano Martinez Peck" <[hidden email]> | Cc: "Dale Henrichs" <[hidden email]>, [hidden email] | Sent: Saturday, December 31, 2011 2:28:51 PM | Subject: Re: about project dependencies | | I'm writing both in the chapter because both work. | You can specify at the baseline and the version the loads: command. | I just forgot that we could do it at the baseline and I thought that | I had to create an extra reference. | | | On Dec 31, 2011, at 3:43 PM, Mariano Martinez Peck wrote: | | > spec | > project: 'XMLSupport' | > with: '1.2.0'. | > | > | > | > | > | > | > | > | > | > -- | > Mariano | > http://marianopeck.wordpress.com | > | > | > | > | | |
fixed
I will need you to read what I wrote. Stef On Jan 3, 2012, at 7:15 PM, Dale Henrichs wrote: > Stef and Mariano, > > I've been on a 'real vacation' (i.e., not touching the computer for almost 10 days ... okay I touched the computer but just to read about basketball and movies ... okay I only fixed one Metacello bug in the first couple of days ... ) and haven't read my mail since before Xmas ... It looks like this discussion has been resolved, but if not let me know and I'll jump in ... > > Dale > > ----- Original Message ----- > | From: "stephane ducasse" <[hidden email]> > | To: "Mariano Martinez Peck" <[hidden email]> > | Cc: "Dale Henrichs" <[hidden email]>, [hidden email] > | Sent: Saturday, December 31, 2011 2:28:51 PM > | Subject: Re: about project dependencies > | > | I'm writing both in the chapter because both work. > | You can specify at the baseline and the version the loads: command. > | I just forgot that we could do it at the baseline and I thought that > | I had to create an extra reference. > | > | > | On Dec 31, 2011, at 3:43 PM, Mariano Martinez Peck wrote: > | > | > spec > | > project: 'XMLSupport' > | > with: '1.2.0'. > | > > | > > | > > | > > | > > | > > | > > | > > | > > | > -- > | > Mariano > | > http://marianopeck.wordpress.com > | > > | > > | > > | > > | > | |
I will and I can't tell you how much I appreciate the work that you and Mariano (and the documentation reviewers) have put into writing the Metacello documentation!
Dale ----- Original Message ----- | From: "stephane ducasse" <[hidden email]> | To: "Dale Henrichs" <[hidden email]> | Cc: [hidden email], "Mariano Martinez Peck" <[hidden email]> | Sent: Tuesday, January 3, 2012 2:09:43 PM | Subject: Re: about project dependencies | | fixed | I will need you to read what I wrote. | | Stef | | On Jan 3, 2012, at 7:15 PM, Dale Henrichs wrote: | | > Stef and Mariano, | > | > I've been on a 'real vacation' (i.e., not touching the computer for | > almost 10 days ... okay I touched the computer but just to read | > about basketball and movies ... okay I only fixed one Metacello | > bug in the first couple of days ... ) and haven't read my mail | > since before Xmas ... It looks like this discussion has been | > resolved, but if not let me know and I'll jump in ... | > | > Dale | > | > ----- Original Message ----- | > | From: "stephane ducasse" <[hidden email]> | > | To: "Mariano Martinez Peck" <[hidden email]> | > | Cc: "Dale Henrichs" <[hidden email]>, | > | [hidden email] | > | Sent: Saturday, December 31, 2011 2:28:51 PM | > | Subject: Re: about project dependencies | > | | > | I'm writing both in the chapter because both work. | > | You can specify at the baseline and the version the loads: | > | command. | > | I just forgot that we could do it at the baseline and I thought | > | that | > | I had to create an extra reference. | > | | > | | > | On Dec 31, 2011, at 3:43 PM, Mariano Martinez Peck wrote: | > | | > | > spec | > | > project: 'XMLSupport' | > | > with: '1.2.0'. | > | > | > | > | > | > | > | > | > | > | > | > | > | > | > | > | > | > | > | > -- | > | > Mariano | > | > http://marianopeck.wordpress.com | > | > | > | > | > | > | > | > | > | | > | | | |
Free forum by Nabble | Edit this page |