Questions regarding org-dependent unlocked packages (Su '20 Release [Beta])
Preface
We are simultaneously trying to do a number of development "firsts" for us, including unlocked packages. Our "happy soup" of metadata is as large as the lake outside our office building; but unfortunately we have too small of a team with major projects happening and in the works, so that none of us can currently spend the desired and necessary time to attempt to organize even the top level of a packaged metadata hierarchy. So the new org-dependent unlocked packages functionality looks very promising to us.
Questions
- After an org-dependent unlocked package is created, can it ever be transitioned to be dependent on a later-created unlocked package?
- If so, what would be the steps?
- If not, what are our options?
Thanks!
@Eric (Moonpie) - you got it right, except the last paragraph.
Let's presume you have metadata X, Y and Z in org-dependent unlocked package p1 version v1.
Here's how you will transition to normal unlocked package.
1) Create an unlocked package (not org-dependent package) p2 version v1. This package contains metadata X, Y and Z.
2) Create version v2 of p1 after removing metadata X, Y and Z. You cannot have an empty package so add a dummy metadata M to v2 of p1.
3) In the installed org, upgrade from p1-v1 to p1-v2. This "releases" X, Y and Z from package p1.
4) In the installed org, install p2-v1. This makes X, Y and Z belong to package p2.
5) Uninstall p1.
