Skip to content

[CI][slang] Rename slang to slang-verilog#50174

Closed
JavierMatosD wants to merge 2 commits into
microsoft:masterfrom
JavierMatosD:ci_file_conflict
Closed

[CI][slang] Rename slang to slang-verilog#50174
JavierMatosD wants to merge 2 commits into
microsoft:masterfrom
JavierMatosD:ci_file_conflict

Conversation

@JavierMatosD
Copy link
Copy Markdown
Contributor

  1. On repology this library is slang-verilog https://aur.archlinux.org/packages/slang-verilog
  2. This port was dumping configs in share/slang which conflicts with another port (shader-slang) https://dev.azure.com/vcpkg/public/_build/results?buildId=127571&view=logs&j=f79cfdd7-47a8-597f-8f57-dc3e21a8f2ad&t=73c5513e-c47c-57a4-379a-581f7e429f13

@JavierMatosD
Copy link
Copy Markdown
Contributor Author

Note: This port was merged two days ago -> #50116

@timkpaine It looks like the configs from this port were in conflict with another port in the registry. I see on repology that this library is referenced as slang-verilog so I'm proposing changing the port name to slang-verilog

@JavierMatosD
Copy link
Copy Markdown
Contributor Author

@BillyONeal @vicroms I could revert the commit that adds this port and re-add it in a new PR?

@BillyONeal
Copy link
Copy Markdown
Member

Note: This port was merged two days ago -> #50116

I think for now we should just deindex it to limit the damage and effectively reopen the original PR.

@BillyONeal
Copy link
Copy Markdown
Member

2. This port was dumping configs in share/slang which conflicts with another port (shader-slang) https://dev.azure.com/vcpkg/public/_build/results?buildId=127571&view=logs&j=f79cfdd7-47a8-597f-8f57-dc3e21a8f2ad&t=73c5513e-c47c-57a4-379a-581f7e429f13

To the best of my understanding renaming the port will not change this.

@JavierMatosD JavierMatosD deleted the ci_file_conflict branch March 5, 2026 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants