You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@egonw that sounds like a plan. I would probably move all of the following repos:
rcdklibs - basically just provides the CDK uberjar
rcdk - functionality on top of the jar
rinchi - maybe obsolete with new CDK code?
fingerprint - i would recommend re-wrapping CDK fingerprints
depict - fns to wrap the DepictionGenerator
I've invited you as the Owner of this organization. You can move the repos and give me Contributor access on the new repos. We can bump a release to add you as the Primary maintainer on each of those packages - I THINK thats all that will be needed for CRAN. On the release side - the jar stuff is straighforward but the build step for CDKR can be a pain.
RCDKLIBS: 20250910 vbump rcdklibs#6 we will not be able to use the standard CRAN release mechanism to host JARs. The size has become a problem and a new way of getting the JARs would be required.
The issue is that CRAN denied us this time. The JAR files have long been well over the size limit of 5MB and for years we have been granted an exception.
To distribute rCDK as a CRAN package we would need an alternative method by which to retrieve and install the JAR files and add them to the rJava class path. The last time I investigated this possibility I couldn't identify a clean way to do this that didn't violate CRANs security policies which limit what a package can do once installed. There are of course direct GitHub installs that can be used but you lose the guarantees, discoverability, testing, and reverse dependency support that CRAN provides.
So current status is that we need an alternate install mechanism and I haven't identified one.
Activity
egonw commentedon Aug 31, 2025
@zachcp, @rajarshi, what about moving it under the hood of the Blue Obelisk? I co-maintain another R package or two and can help out.
rajarshi commentedon Sep 1, 2025
I'd be open to that
zachcp commentedon Sep 2, 2025
I think that's a great idea. What do you need? And thank you
egonw commentedon Sep 3, 2025
I would suggest:
egonw commentedon Sep 9, 2025
@rajarshi, @zachcp, shall I go ahead?
rajarshi commentedon Sep 9, 2025
Yes, fine from my side. But as @zachcp is the current maintainer, I'd look for confirmation from him
zachcp commentedon Sep 11, 2025
@egonw that sounds like a plan. I would probably move all of the following repos:
I've invited you as the Owner of this organization. You can move the repos and give me Contributor access on the new repos. We can bump a release to add you as the Primary maintainer on each of those packages - I THINK thats all that will be needed for CRAN. On the release side - the jar stuff is straighforward but the build step for CDKR can be a pain.
zachcp commentedon Sep 11, 2025
Egon let's hold on moving these repos until I'm finished with the releases
zachcp commentedon Nov 30, 2025
So the current status is:
egonw commentedon Jul 1, 2026
@zachcp, can you give an update? It seems we have a regression, and I am getting rJava errors:
Specifically, can I move and take over the packages?
zachcp commentedon Jul 3, 2026
Hi @egonw,
The issue is that CRAN denied us this time. The JAR files have long been well over the size limit of 5MB and for years we have been granted an exception.
To distribute rCDK as a CRAN package we would need an alternative method by which to retrieve and install the JAR files and add them to the rJava class path. The last time I investigated this possibility I couldn't identify a clean way to do this that didn't violate CRANs security policies which limit what a package can do once installed. There are of course direct GitHub installs that can be used but you lose the guarantees, discoverability, testing, and reverse dependency support that CRAN provides.
So current status is that we need an alternate install mechanism and I haven't identified one.
Zach cp