I&#39;m not sure whether this is one of the goals of the community or whether maybe someone&#39;s already heading in this direction, but something like Gofer install: #myPackage that looked up which repo and version are the suitable ones would really rock big time.��The apt-get of Pharo, call it...<div>

<br></div><div>To go on with the apt metaphor, Gofer search: &#39;whatever&#39; could return a list of packages the descriptions/names of which matched &#39;whatever&#39;.</div><div><br></div><div>What do you think?</div>

<div><div><br><div class="gmail_quote">2011/8/17 Johan Brichau <span dir="ltr">&lt;<a href="mailto:johan@inceptive.be">johan@inceptive.be</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Maybe a bit of wishful thinking but���<br>
<br>
Ideally, I think of the metacellorepository as a kind of &#39;smart folder&#39; where all metacello configurations of public repositories are automatically included.<br>
Something like a smart mail folder on mac mail.<br>
<br>
Having two locations with the same package almost always leads to confusion / mistakes / forgetting / etc���<br>
<br>
Would such an &#39;automatic&#39; repository be possible to implement in squeaksource3 and/or smalltalk hub?<br>
<font color="#888888"><br>
Johan<br>
</font><div><div></div><div class="h5"><br>
On 17 Aug 2011, at 20:01, St��phane Ducasse wrote:<br>
<br>
&gt;<br>
&gt; The policy should be<br>
&gt; �� �� �� - put a configurationOf in your package<br>
&gt; �� �� �� - publish when you want a copy of it in metacellorepository<br>
&gt;<br>
&gt; I will sit with dale sunday because we want the &quot;publish&quot; to copy all the dependent package also in the DistributionMetacelloRepository<br>
&gt;<br>
&gt; On Aug 17, 2011, at 8:59 AM, Max Leske wrote:<br>
&gt;<br>
&gt;&gt; I would like to complain a bit about the current way Metacello configurations are distributed in different repositories. I ended up using the wrong configuration for two different projects twice in just two days. Apart from the date in the configuration file (and possibly the version number, although that&#39;s not as reliable) there&#39;s no easy way to tell which configuration is the most recent.<br>


&gt;&gt;<br>
&gt;&gt; Some people seem to have adopted MetacelloRepository as the standard repository for all configurations, others keep the configuration for a project in the project repositories and a third group uses both repositories (where one repository contains outdated versions of course���).<br>


&gt;&gt;<br>
&gt;&gt; Can we please agree on a simple policy on where to store the configuration for a project? I am sure that this would make life easier for all of us.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; Max<br>
&gt;<br>
&gt;<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Bernat Romagosa.<br>
</div></div>