Re: upgrade process for big sur/dpkg1.16

> On Aug 28, 2020, at 02:42, Hanspeter Niederstrasser <[email protected]> wrote:
> 
> What's the upgrade process for the dpkg1.16 branch and the dists tree?
> 
> Several packages are now essential (e.g. time-date-pm and xz) and will have to be moved from their present subfolders in dists to 'base'. Also, some base packages have newer versions than what's in the dpkg1.16 branch source (e.g. libiconv and texinfo). But the dpkg1.16 branch versions have needed changes that might be incompatible with older fink installs, so we can't just copy what's currently in dist to the dpkg1.16 branch, or push the dpkg1.16 branch versions directly into dists. Or are dpkg1.16 packages compatible with legacy dpkg?
> 
> Hanspeter
> 
> 


At minimum, the most logical thing to do would be to update libiconv, texinfo, et. al. in the dpkg1.16 branch and also apply the branch-specific changes - i.e. merge them in a logical sense if not in a Git sense.  I hate to say it, but this might be a case for a new distro and clean reinstall rather than update in place.  I know we just did that for Catalina, but my impression is that Big Sur is going to change a bunch of stuff.

-- 
Alexander Hansen, Ph.D.
Fink User Liaison



_______________________________________________
fink-core mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core