Yep,

A metacello 1.0-beta.25 bug ... I'll fix it right now (or after breakfast:).

Dale
----- "Dale Henrichs" <[email protected]> wrote:

| If that's the build process you use, I'm not sure why the repsitory
| isn't mapped correctly ... maybe it's a metacello bug then...I will do
| a build and see what I can find out...
| 
| Dale
| ----- "Mariano Martinez Peck" <[email protected]> wrote:
| 
| | On Sun, Mar 21, 2010 at 6:36 PM, Dale Henrichs
| | <[email protected]>wrote:
| |
| | > Mariano,
| | >
| | > I am seriously considering releasing 1.0-beta.25 today ... I have
| | smacked
| | > the heck out Metacello over the last three days without issues so
| | I'm
| | > thinking I can let this puppy out the door:)...Especially if it
| will
| | clean
| | > up the release process...
| | >
| | > One other point I have noticed is that the following
| configurations
| | aren't
| | > pointing to the correct repository:
| | >
| | >  ConfigurationOfOmniBrowser
| | >  ConfigurationOfRefactoringBrowser
| | >  ConfigurationOfOCompletion
| | >  ConfigurationOfShout
| | >  ConfigurationOfProfStef
| | >
| | > They all reference the package-cache instead of SqueakSource
| | > MetacelloRepository.
| | >
| |
| |
| | Thanks Dale. I didn't realise about that.
| |
| |
| | >
| | > I'm assuming this is because they were in your package-cache when
| | you did
| | > the build.
| | >
| | >
| | No. I take a PharoCore image which is zip, without even the
| | package-cache
| | folder and then I evaluate what you can see in installScript, which
| is
| | :
| |
| | Gofer new
| |     gemsource: 'metacello';
| |     package: 'ConfigurationOfMetacello';
| |     load.
| |
| |
| | ((Smalltalk at: #ConfigurationOfMetacello) project version:
| | '1.0-beta.25')
| | perform: #load.
| |
| | Gofer new
| |     squeaksource: 'MetacelloRepository';
| |     package: 'ConfigurationOfPharo';
| |     load.
| |
| | ((Smalltalk at: #ConfigurationOfPharo) project version:
| | '1.0-rc3.10515')
| | perform: #silently: with: true; perform: #load.
| |
| |
| | > I think this is happening because of a recent change in the
| sorting
| | order
| | > for Gofer ...
| | >
| | >
| | I have no idea.
| |
| |
| | > For the build process you may want to either make sure your
| | package-cache
| | > is empty
| |
| |
| |
| | My package-cache was empty. I even didn't have that folder-
| |
| |
| | > or use disablePackageCache in the places where you explicitly load
| | a
| | > Configuration or perhaps something else?
| | >
| | >
| | How can I do that ? where should I put disablePackageCache ? do you
| | have a
| | example?
| |
| | Thanks!
| |
| | Mariano
| |
| |
| |
| | > Dale
| | >
| |
| |
| | > ----- "Mariano Martinez Peck" <[email protected]> wrote:
| | >
| | > | >
| | > | > I see that the installScript uses ConfigurationOfMetacello
| from
| | > | > gemsource metacello repository instead of Metacello
| repository.
| | > | Given
| | > | > that this will be the final release of 1.0, shouldn't we copy
| | > | > ConfigurationOfMetacello to squeaksource/MetacelloRepository
| so
| | that
| | > | the
| | > | > package registered in monticello is this instead of the
| | gemstone
| | > | one.
| | > | > This repo for ConfigurationOfMetacello overrides the one of
| | > | PharoCore
| | > | > that points to squeaksource.
| | > | >
| | > | > Dale, can you put this version in squeaksource. The release is
| | very
| | > | > close and anyway it will be shipped in Pharo dev 1.0, so will
| | reach
| | > | a
| | > | > lot of people, even if not on squeaksource
| | > | >
| | > | >
| | > | Yes. This is because I added the ImageForDevelopers in the
| group.
| | With
| | > | that,
| | > | when running headless I have the problem with the progress Bar.
| | > | Then, i needed to use the silntly method, which is in Metacello
| | > | beta.25
| | > | which is not released yet. That's why I have to put the other
| | one.
| | > |
| | > | Don't worry that beta.25 will be then correctly uploaded and
| | released.
| | > | After
| | > | that, the installScript will be even simpler as I won't need to
| | > | install
| | > | Metacello manually, but with the ensureMetacello ;)
| | > |
| | > | Cheers
| | > |
| | > | Mariano
| | > |
| | > |
| | > |
| | > | > Cheers
| | > | > >
| | > | > > Mariano
| | > | > >
| | > | > > _______________________________________________
| | > | > > Pharo-users mailing list
| | > | > > [email protected]
| | > | > >
| | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
| | > | >
| | > | > --
| | > | > Miguel Cobá
| | > | > http://miguel.leugim.com.mx
| | > | >
| | > | >
| | > |
| | > | _______________________________________________
| | > | Pharo-project mailing list
| | > | [email protected]
| | > |
| | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
| | >
| | > _______________________________________________
| | > Pharo-project mailing list
| | > [email protected]
| | >
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
| 
| _______________________________________________
| Pharo-project mailing list
| [email protected]
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to