[Cuis-dev] Something strange going on with package dependency version numbers

Juan Vuletich juan at jvuletich.org
Fri Oct 11 08:58:01 PDT 2019


On 10/11/2019 11:57 AM, ken.dickey--- via Cuis-dev wrote:
> On 2019-10-10 18:36, Phil B via Cuis-dev wrote:
>
>> Ugh/yay! It's not a new bug...  it's a fix exposing issues from the 
>> old one.
>
> Hi Phil,
>
> I am currently out with a bad cold, so a proper fix will take me a bit 
> longer.
>
> FYI, there are a couple of things on my list to take care of.
>   [1] Caching FeatureSpec's of a Package when scanned
>   [2] Making checks more strict.
>
> I did a short-cut for the current code by just checking feature names 
> when adding FeatureSpec's to the SortedCollection of Packages to 
> load.  When comparing, I need to use the most strict FeatureSpec 
> rather than just checking the names.
>
> Simple to fix, but I have been busy of late.  Ya, always.
>
> One feature we could add.  Right now one can use the FileList to 
> re-load an already loaded Package.  This re-checks dependencies but 
> always loads the indicated Package.
>
> Would it be helpful/useful/not-too-confusing to have an option to 
> re-load all dependencies?
>
> My take is that this would break more things than it would help, as an 
> updated dependent from one Package might break something in another, 
> already loaded, Package which also requires that dependency.
>
> One hopes in the typical case to only be updating a package at a time 
> and if making a cluster of edits (e.g. with StyledTextEditor 
> components) one could re-load a Package at a time from the FileList.
>
> Starting from a fresh image and re-loading all Packages from their 
> Features seems to me to be the simplest solution.
>
> Well, as you can perhaps tell, my head is stuffed and my thinking 
> muddled.
>
> I'll let you "pre-flight" my fix(es) as I get there.
>
> Thanks again for you patience and resiliency..
> -KenD

Hi Folks,

Please note that I also did some tweaks in 3907 and 3908. Still, I 
believe that the problem Phil sees is an invalid requirement spec, and 
in a separate message I just described possible steps to reproduce, and 
proposed fix. Please check them.

Thanks,

-- 
Juan Vuletich
www.cuis-smalltalk.org
https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev
https://github.com/jvuletich
https://www.linkedin.com/in/juan-vuletich-75611b3
@JuanVuletich



More information about the Cuis-dev mailing list