[Cuis-dev] Packages Held Back
ken.dickey at whidbey.com
ken.dickey at whidbey.com
Sat Jun 1 13:57:59 PDT 2024
On 2024-06-01 12:53, Hilaire Fernandes wrote:
> Will not the Feature #require:version: discard the version from
> Cuis6-2?
The Current RequireEmpty requires the Current Empty package:
!provides: 'RequireEmpty' 1 0!
!requires: 'Empty' 1 2 nil!
The Stable/HeldPackage requires an earlier Empty package:
!provides: 'RequireEmpty' 1 0!
!requires: 'Empty' 1 1 nil!
Doing `Feature require: 'RequireEmpty'.` in the 7.0 Workspace happens to
find the _RequireEmpty_ package in the
Cuis6-2/HeldPackages6-2/EmptyStuff before looking in the EmptyStuff
directory in the Cuis-Smalltalk dir.
It then looks for Empty package 1.1 which
!requires: 'Cuis-Base' 62 6156 68!
and so chokes.
Loading the package Cuis-Smalltalk/EmptyStuff/RequireEmpty.pck.st from
the file list asks for Empty package 1.2, so the package
Cuis6-2/HeldPackages6-2/EmptyStuff/Empty.pck.st _is_ indeed ignored as
being the wrong version and the search continues to find the right one.
So, one way to deal with Stable releases is to have Cuis-Stable6-2, go
there and clone Cuis6-2, invoke a local clonePackageRepos.sh which pulls
the proper repo versions, and not have Cuis-Smalltalk-Dev or Cuis7-0
within the same parent directory (Cuis-Stable6-2). Again, have
completely distinct file trees for each of Current, 6-2, 7-0, ..
How best to avoid confusion...
-KenD
More information about the Cuis-dev
mailing list