[Cuis-dev] Beta for Cuis 7.0 stable, Rolling Release is 7.1

[ken.dickey at whidbey.com]

On 2024-05-20 05:56, Hilaire Fernandes via Cuis-dev wrote:

> Does this stable release 7.0 capture the state of the third party 
> packages?

One possibility.  Let's think about this.. Two Parts

Part One: We "fork" a package because of version difference between 
Stable and Current..

   [0] Copy the Package to be held back.  This will become a new Package 
in the same GIT location.
   [1] Change the Name of the package to be held back
(e.g. 'IA-EN-Dictionary.pck.st' to 'IA-EN-Dictionary-pre7.0.pck.st')
   [2] Manually change the package text so the the 'provides:' name 
matches.
(e.g. '!provides: 'IA-EN-Dictionary-pre7.0' 1 27!`)
   [3] Change (or add) a '!requires:' for Cuis-Base to END before the 
latest
(e.g. `!requires: 'Cuis-Base' 60 5552 60 6000!`)
   [4] Add this new Package in GIT at the place/directory it's sibling 
lives.

Part Two: We update Feature to add Feature>>require:maxBase:

   The new method allows us to just specify the max/end-cap base release
   so that we don't have to manually update the transitive requirements.
(e.g. `Feature require: 'IA-EN-Dictionary' maxBase: 7.0`)

I am not wedded to the details here.  E.g. how to fork+mark a 'held 
back' package.

What I would like is [a] simple to explain and [b] simple to use.

It would be nice to have the Installed Packages Browser do the 
mechanics.

Options? Refinements?

I'm sure you can think of something..
-KenD