Automatically find dependencies
Locked
Automatically find dependencies
 
|
I was playing with one of Lukas's projects that shows you what other
packages a package depends on (although it doesn't take into account extension methods). It would be super cool if Metacello's tools (esp. the eventual UI) pre-populated these. Here's an example: Gofer new renggli: 'packaging'; package: 'Package-Dependencies'; load. a := PDPackageAnalyzer onPackagesNamed: #('Refactoring-Environment'). r := a relation removeInternalDependencies; combineDependencies; reduce. dependencyPackageInfos := (r outgoing collect: [ :dep | dep target info ]) asSet. |
Re: Automatically find dependencies
|
|
The does consider extension methods, but only across the packages
specified in the arguments. So if you have only #('Refactoring-Environment') specified, the code considers all other packages as "the system". Lukas On 30 December 2011 14:53, Sean DeNigris <[hidden email]> wrote: > I was playing with one of Lukas's projects that shows you what other > packages a package depends on (although it doesn't take into account > extension methods). It would be super cool if Metacello's tools (esp. > the eventual UI) pre-populated these. Here's an example: > > Gofer new > renggli: 'packaging'; > package: 'Package-Dependencies'; > load. > > a := PDPackageAnalyzer onPackagesNamed: #('Refactoring-Environment'). > r := a relation > removeInternalDependencies; > combineDependencies; > reduce. > dependencyPackageInfos := (r outgoing collect: [ :dep | dep target > info ]) asSet. -- Lukas Renggli www.lukas-renggli.ch |
|
|
In reply to this post by Sean DeNigris
We are currently working on Versionner. This is indeed something that I have in mind for a while already.
Be ready for a very cool configuration management tool in a couple of weeks! Happy new year to all of you! Alexandre On 30 Dec 2011, at 10:53, Sean DeNigris wrote: > I was playing with one of Lukas's projects that shows you what other > packages a package depends on (although it doesn't take into account > extension methods). It would be super cool if Metacello's tools (esp. > the eventual UI) pre-populated these. Here's an example: > > Gofer new > renggli: 'packaging'; > package: 'Package-Dependencies'; > load. > > a := PDPackageAnalyzer onPackagesNamed: #('Refactoring-Environment'). > r := a relation > removeInternalDependencies; > combineDependencies; > reduce. > dependencyPackageInfos := (r outgoing collect: [ :dep | dep target > info ]) asSet. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
Re: Automatically find dependencies
|
|
On Fri, Dec 30, 2011 at 10:16 PM, Alexandre Bergel <[hidden email]> wrote: We are currently working on Versionner. This is indeed something that I have in mind for a while already. The tool is on top of Metacello ? Happy new year to all of you! -- Mariano http://marianopeck.wordpress.com |
|
|
Alexandre
|
Re: Automatically find dependencies
|
|
Hi Alex,
Sounds like fun. Can I interest you to join efforts and build your mechanisms on top of GTMetaceller (part of the Glamorous Toolkit)? Cheers, Doru On 30 Dec 2011, at 23:28, Alexandre Bergel wrote: >> The tool is on top of Metacello ? > > Yes. And we will probably provide a very nice feature: a caching mechanism for which one .mcz for all the download packages, for a particular version. This cache should be completely transparent. The end user will simply see a gain in performance. > > Alexandre > > >> >> Happy new year to all of you! >> Alexandre >> >> >> On 30 Dec 2011, at 10:53, Sean DeNigris wrote: >> >> > I was playing with one of Lukas's projects that shows you what other >> > packages a package depends on (although it doesn't take into account >> > extension methods). It would be super cool if Metacello's tools (esp. >> > the eventual UI) pre-populated these. Here's an example: >> > >> > Gofer new >> > renggli: 'packaging'; >> > package: 'Package-Dependencies'; >> > load. >> > >> > a := PDPackageAnalyzer onPackagesNamed: #('Refactoring-Environment'). >> > r := a relation >> > removeInternalDependencies; >> > combineDependencies; >> > reduce. >> > dependencyPackageInfos := (r outgoing collect: [ :dep | dep target >> > info ]) asSet. >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> -- www.tudorgirba.com "Speaking louder won't make the point worthier." |
|
|
We indeed planned to use glamour for the ui. It is so much convenient. I was not aware of gtmetaceller. We will have a look at it.
Alexandre Le 30 déc. 2011 à 19:47, Tudor Girba <[hidden email]> a écrit : > Hi Alex, > > Sounds like fun. Can I interest you to join efforts and build your mechanisms on top of GTMetaceller (part of the Glamorous Toolkit)? > > Cheers, > Doru > > > On 30 Dec 2011, at 23:28, Alexandre Bergel wrote: > >>> The tool is on top of Metacello ? >> >> Yes. And we will probably provide a very nice feature: a caching mechanism for which one .mcz for all the download packages, for a particular version. This cache should be completely transparent. The end user will simply see a gain in performance. >> >> Alexandre >> >> >>> >>> Happy new year to all of you! >>> Alexandre >>> >>> >>> On 30 Dec 2011, at 10:53, Sean DeNigris wrote: >>> >>>> I was playing with one of Lukas's projects that shows you what other >>>> packages a package depends on (although it doesn't take into account >>>> extension methods). It would be super cool if Metacello's tools (esp. >>>> the eventual UI) pre-populated these. Here's an example: >>>> >>>> Gofer new >>>> renggli: 'packaging'; >>>> package: 'Package-Dependencies'; >>>> load. >>>> >>>> a := PDPackageAnalyzer onPackagesNamed: #('Refactoring-Environment'). >>>> r := a relation >>>> removeInternalDependencies; >>>> combineDependencies; >>>> reduce. >>>> dependencyPackageInfos := (r outgoing collect: [ :dep | dep target >>>> info ]) asSet. >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > |
Re: Automatically find dependencies
|
|
In reply to this post by Tudor Girba-2
It means that people not loading metacello will not use it.
Sad no? Stef On Dec 30, 2011, at 11:47 PM, Tudor Girba wrote: > Hi Alex, > > Sounds like fun. Can I interest you to join efforts and build your mechanisms on top of GTMetaceller (part of the Glamorous Toolkit)? > > Cheers, > Doru > > > On 30 Dec 2011, at 23:28, Alexandre Bergel wrote: > >>> The tool is on top of Metacello ? >> >> Yes. And we will probably provide a very nice feature: a caching mechanism for which one .mcz for all the download packages, for a particular version. This cache should be completely transparent. The end user will simply see a gain in performance. >> >> Alexandre >> >> >>> >>> Happy new year to all of you! >>> Alexandre >>> >>> >>> On 30 Dec 2011, at 10:53, Sean DeNigris wrote: >>> >>>> I was playing with one of Lukas's projects that shows you what other >>>> packages a package depends on (although it doesn't take into account >>>> extension methods). It would be super cool if Metacello's tools (esp. >>>> the eventual UI) pre-populated these. Here's an example: >>>> >>>> Gofer new >>>> renggli: 'packaging'; >>>> package: 'Package-Dependencies'; >>>> load. >>>> >>>> a := PDPackageAnalyzer onPackagesNamed: #('Refactoring-Environment'). >>>> r := a relation >>>> removeInternalDependencies; >>>> combineDependencies; >>>> reduce. >>>> dependencyPackageInfos := (r outgoing collect: [ :dep | dep target >>>> info ]) asSet. >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > |
Re: Automatically find dependencies
|
|
Hi Stef,
I do not understand what you are saying. What is sad? Doru On 31 Dec 2011, at 08:53, stephane ducasse wrote: > It means that people not loading metacello will not use it. > Sad no? > > Stef > > > On Dec 30, 2011, at 11:47 PM, Tudor Girba wrote: > >> Hi Alex, >> >> Sounds like fun. Can I interest you to join efforts and build your mechanisms on top of GTMetaceller (part of the Glamorous Toolkit)? >> >> Cheers, >> Doru >> >> >> On 30 Dec 2011, at 23:28, Alexandre Bergel wrote: >> >>>> The tool is on top of Metacello ? >>> >>> Yes. And we will probably provide a very nice feature: a caching mechanism for which one .mcz for all the download packages, for a particular version. This cache should be completely transparent. The end user will simply see a gain in performance. >>> >>> Alexandre >>> >>> >>>> >>>> Happy new year to all of you! >>>> Alexandre >>>> >>>> >>>> On 30 Dec 2011, at 10:53, Sean DeNigris wrote: >>>> >>>>> I was playing with one of Lukas's projects that shows you what other >>>>> packages a package depends on (although it doesn't take into account >>>>> extension methods). It would be super cool if Metacello's tools (esp. >>>>> the eventual UI) pre-populated these. Here's an example: >>>>> >>>>> Gofer new >>>>> renggli: 'packaging'; >>>>> package: 'Package-Dependencies'; >>>>> load. >>>>> >>>>> a := PDPackageAnalyzer onPackagesNamed: #('Refactoring-Environment'). >>>>> r := a relation >>>>> removeInternalDependencies; >>>>> combineDependencies; >>>>> reduce. >>>>> dependencyPackageInfos := (r outgoing collect: [ :dep | dep target >>>>> info ]) asSet. >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >> >> -- >> www.tudorgirba.com >> >> "Speaking louder won't make the point worthier." >> > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go." |
Re: Automatically find dependencies
|
|
> Hi Stef, > > I do not understand what you are saying. What is sad? Because it means that people not loading Glamour will not have a good tools for Metacello. > > Doru > > > On 31 Dec 2011, at 08:53, stephane ducasse wrote: > >> It means that people not loading metacello will not use it. >> Sad no? >> >> Stef >> |
Re: Automatically find dependencies
|
|
Hi Stef,
Ok, you meant Glamour, not Metacello. You seem to say that it is bad that Glamour provides a good infrastructure that appeals to people. Maybe a better conclusion is that Glamour is something to be considered for the infrastructure of Pharo. Doru On 31 Dec 2011, at 12:24, stephane ducasse wrote: > > >> Hi Stef, >> >> I do not understand what you are saying. What is sad? > > Because it means that people not loading Glamour will not have a good tools for Metacello. > >> >> Doru >> >> >> On 31 Dec 2011, at 08:53, stephane ducasse wrote: >> >>> It means that people not loading metacello will not use it. >>> Sad no? >>> >>> Stef >>> > -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut." |
Re: Automatically find dependencies
|
|
On Dec 31, 2011, at 1:00 PM, Tudor Girba wrote: > Hi Stef, > > Ok, you meant Glamour, not Metacello. > > You seem to say that it is bad that Glamour provides a good infrastructure that appeals to people. Maybe a better conclusion is that Glamour is something to be considered for the infrastructure of Pharo. Do you think so? I do not think that we can base our infrastructure on something that only one person understand and can modify. You will tell that this is the same for Morphic but this is not true. Stef |
Re: Automatically find dependencies
|
|
In reply to this post by Lukas Renggli
On Dec 30 2011, 10:46 am, Lukas Renggli <[hidden email]> wrote:
> The does consider extension methods Cool! But how does it know whether a send is to an extension method or non-extension with the same selector? |
«
Return to Metacello
|
1 view|%1 views
| Free forum by Nabble | Edit this page |