[Cuis-dev] Something strange going on with package dependency version numbers
Juan Vuletich
juan at jvuletich.org
Sat Oct 12 07:28:35 PDT 2019
(snip)
On 10/11/2019 9:29 PM, Phil B wrote:
> Juan,
>
> ...
>
> OK, I applied both your update and Ken's and it's definitely an
> improvement. A few things I noticed:
>
> 1) Using my Foo/Bar package example I get:
>
> Could not find package supplying: FeatureRequirement(Bar 1.2 to *.*)
> Required by: FeatureRequirement(Foo *.*)) For installing:
> FeatureRequirement(Foo *.*))
>
> Is there going to be a case where the 'required by:' and 'installing:'
> items can be different?
Yes. When the requirement chain that fails has 3 or more elements.
'Required by' is the package that asked for the failed requirement. 'For
installing' is the root package you are trying to install.
> (this actually relates to my next item which I meant to mention re:
> previous changes) If so, could we only display both when they
> differ? If not, then you're just listing the feature twice.
Sure, please check #requireUnlessIn:main:requiringFeature:, tweak it to
suit your taste and repost. Thanks!
> 2) Something that used to be legal was that I could have a package
> named FooAlternate which provides: Foo. Now it appears that the
> package and feature name must match. I've actually been meaning to
> bring up for a while that I'd like packages to have better support for
> package name/provides mismatches, not removing the capability
> entirely... it's a useful option.
Yes... That would be nice to have. Maybe we can allow package names that
have the feature name as a prefix, meaning that they match
'FeatureName*'. This would still let us avoid scanning every .pck.st
file just in case.
> 3) When you attempt to update a requirement to an unsaved package
> version you get a dialog with proceed and abandon buttons. The option
> to proceed doesn't really make sense unless the intent was to allow
> the user to override (i.e. force updating to) of the unsaved version
> which it (currently) does not.
That's because of using #notify: Maybe we'd call #inform: instead.
>
> Thanks,
> Phil
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