Conversation
|
I see if I can offline figure out to make it compatible with latest yosys |
There was a problem hiding this comment.
Is this package actually broken or simply "unmaintained"?
If it still builds, marking is as broken is not the right action.
Also, is there an official statement from upstream stating that development has stopped? Or is your observation just based on the date of the latest commit?
If it is indeed "archived/unmaintained" AND if it does not make any sense to keep it around, then we should properly drop the package. This means removing the files and adding an entry in pkgs/top-level/aliases.nix.
It's broken with newer yosys and is the only reason (after you merged my patch for silice) to not update yosys.
The last commit is from Dec 2024, and I emailed the main commiter: No answer.
I would vote to drop it; if the maintainer steps up again it should be easily ressurected, right? |
If @hzeller agrees, then sure, let's drop it. |
|
Correct commit message would be: |
|
Drop sounds like a good choice for now. |
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release-25.11
git worktree add -d .worktree/backport-473242-to-release-25.11 origin/release-25.11
cd .worktree/backport-473242-to-release-25.11
git switch --create backport-473242-to-release-25.11
git cherry-pick -x 0f1f388f3259d652dab39d6362da364a7c73199b |
This is a package removal; backporting to stable is not necessary as it would be a breaking change for 25.11 users. |
Synlig has stopped development, that last commit is from Dec 2024, it seems yosys-slang is used nowadays.