Bill,

Looks like ConfgurationOfCitezen does need required projects added (I am 
willing to help the maintainers - drop me a line).

Perhaps the configs aren't ready for prime time and that's why they have not 
been added to MetacelloRepository.

You can add repositories to your own GoferProject:

  Gofer project repository: 'Repository URL'.

Will add another repository to the search path.

Dale
----- "Wilhelm K Schwab" <[email protected]> wrote:

| Hello all,
| 
| Some time ago, there was (I thought) a patch for saving workspace text
| to a file; I had hoped to find that in 1.0, but it is not in RC3 that
| I can find.
| 
| The first thing I did was load the Loader extensions to Gofer.  It
| installed as expected.  I have not looked into the code, but tried
| #search: and found things like Citezen and Rio missing.  That might be
| "simply" because the Configuration* packages are not in the Metacello
| repository??  If so, are they not there for a non-trivial reason?
| 
| I then grabbed ConfigurationOfCitezen, and was hung up by an
| unsatisfied dependence on SmaCC. The SmaCC runtime is in my RC1 image,
| but I don't know how/why it was loaded; presumably CZLoader did it.
| 
| Are these bugs or features?  I am leaning toward bugs, but the
| question is whether any or all of the following appicable: (1)
| ConfigurationOfCitezen needs to load prerequisites; (2) Loader is in
| the wrong to not see them; (3) I need to add repositories to Loader;
| (4) various ConfigurationOf* packages need to be in the Metacello
| repository.
| 
| Any ideas?
| 
| Bill
| 
| 
| _______________________________________________
| 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