Dear Duncan,
Thanks for spending time on this. You are right that there were some
incompatibility issues for people with old spatstat installed along
side spatstat., and we might have been fix some of that, but it was
not completely clear to us. However, the problem is now solved as
spatstat 2
One part of your first message that I don't understand is the reluctance
of downstream package writers to update to the spatstat. versions.
You said "Many have reported back that they have a new version ready
that will work with spatstat (>=2.0) and are waiting to submit until it
is on CRA
Dear Duncan,
Thanks for taking the time to read my message and for the constructive
idea. You are right that it is a bit late for us to do this now. Given
that spatstat (<=1.65) exports >2,500 objects which are now spread
across sub-packages we would obviously have to make a script to help us
reex
It may be too late to do this now, but you could use the approach that
devtools used when it was broken up: The main package imports functions
from the new spatstat. packages and exports them. This way it could
be done with no breaking changes. Reverse dependencies could change to
depend
