Monticello Package Dependencies [Was: Re: ClockAndCalendarMorphs project on SqueakSource]

> On 01-02-2018, at 9:58 AM, Eliot Miranda <[hidden email]> wrote:
>
>
>
> On Thu, Feb 1, 2018 at 7:48 AM, Jakob Reschke <[hidden email]> wrote:
> I have been told that nobody uses the Monticello feature of
> dependencies among packages...
>
> At least for me that's because I didn't know they supported this :-(.  I think I shall try using it :-)

I do (or at least, did, might have stopped at some point, get off my lawn) use it for the WeatherStation package and NuScratchGPIO. The ui is a bit … sparse. Functionally it seems to work quite nicely; it loads the required packages before the main package. What else would it do? A bit more UI to manage required packages would be nice; currently you can add one, or remove them all. A bit sledge-hammer for my tastes.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Never trust a computer you can't lift.

On Thu, Feb 1, 2018 at 10:35 AM, tim Rowledge <[hidden email]> wrote:

> On 01-02-2018, at 9:58 AM, Eliot Miranda <[hidden email]> wrote:
>
>
>
> On Thu, Feb 1, 2018 at 7:48 AM, Jakob Reschke <[hidden email]> wrote:
> I have been told that nobody uses the Monticello feature of
> dependencies among packages...
>
> At least for me that's because I didn't know they supported this :-(.  I think I shall try using it :-)

I do (or at least, did, might have stopped at some point, get off my lawn) use it for the WeatherStation package and NuScratchGPIO. The ui is a bit … sparse. Functionally it seems to work quite nicely; it loads the required packages before the main package. What else would it do? A bit more UI to manage required packages would be nice; currently you can add one, or remove them all. A bit sledge-hammer for my tastes.

We at least need to reveal it through the Monticello browser.  I see no Dependences button or edit dependencies menu item anywhere.  So for me the feature was completely invisible.  I've been maintaining unnecessary load scripts for the VMMaker package when I could simply rely on dependencies.  This isn't good guys :-(

> On 02-02-2018, at 11:35 AM, Bert Freudenberg <[hidden email]> wrote:
>
> On 2 February 2018 at 19:38, Eliot Miranda <[hidden email]> wrote:
>
>
> On Thu, Feb 1, 2018 at 10:35 AM, tim Rowledge <[hidden email]> wrote:
>
>
> > On 01-02-2018, at 9:58 AM, Eliot Miranda <[hidden email]> wrote:
> >
> >
> >
> > On Thu, Feb 1, 2018 at 7:48 AM, Jakob Reschke <[hidden email]> wrote:
> > I have been told that nobody uses the Monticello feature of
> > dependencies among packages...
> >
> > At least for me that's because I didn't know they supported this :-(.  I think I shall try using it :-)
>
> I do (or at least, did, might have stopped at some point, get off my lawn) use it for the WeatherStation package and NuScratchGPIO. The ui is a bit … sparse. Functionally it seems to work quite nicely; it loads the required packages before the main package. What else would it do? A bit more UI to manage required packages would be nice; currently you can add one, or remove them all. A bit sledge-hammer for my tastes.
>
> We at least need to reveal it through the Monticello browser.  I see no Dependences button or edit dependencies menu item anywhere.  So for me the feature was completely invisible.  I've been maintaining unnecessary load scripts for the VMMaker package when I could simply rely on dependencies.  This isn't good guys :-(
>
> ​It's the first menu item "add required package".
>
> Don't use it. There's a reason we use config maps or metacello instead of these.

Then the facility should have been removed some time ago.