GitHub will discontinue Subversion support, which is the basis of all the packages hosted in KLayout (https://github.blog/2023-01-20-sunsetting-subversion-support/). KLayout uses the SVN interface to download the package data.
As a quick mitigation, it is possible to host packages on SourceForge with Subversion selected as the code tool. This will mean manual effort upon releasing GitHub-hosted projects. This used to be very convenient with the subversion bridge.
To facilitate this migration I will add SourceForge to the package repositories and remove GitHub.
Important: Existing packages will be transferred to a read-only KLayout-owned SVN repository so they will continue working.
As a long-term solution, I plan to add Git support for package download. That means:
- It will again be possible to deploy KLayout packages directly from GitHub
- KLayout packages have to reside at the top level of a Git repo (specifically:
grain.xml needs to be located at top level). So far, it was possible to use a sub-folder as the package home. This will no longer work. A workaround is to use a Git submodule for the package part.
- This deployment path will only work for new KLayout versions (target is 0.29)
Please also see this discussion: https://www.klayout.de/forum/discussion/2399/red-alert-klayout-package-manager-will-stop-working-beginning-of-2024-with-github-hosted-packages#latest
Matthias
GitHub will discontinue Subversion support, which is the basis of all the packages hosted in KLayout (https://github.blog/2023-01-20-sunsetting-subversion-support/). KLayout uses the SVN interface to download the package data.
As a quick mitigation, it is possible to host packages on SourceForge with Subversion selected as the code tool. This will mean manual effort upon releasing GitHub-hosted projects. This used to be very convenient with the subversion bridge.
To facilitate this migration I will add SourceForge to the package repositories and remove GitHub.
Important: Existing packages will be transferred to a read-only KLayout-owned SVN repository so they will continue working.
As a long-term solution, I plan to add Git support for package download. That means:
grain.xmlneeds to be located at top level). So far, it was possible to use a sub-folder as the package home. This will no longer work. A workaround is to use a Git submodule for the package part.Please also see this discussion: https://www.klayout.de/forum/discussion/2399/red-alert-klayout-package-manager-will-stop-working-beginning-of-2024-with-github-hosted-packages#latest
Matthias