Hello! I must admit, I completely forgot about port dependencies in that direction... Thank you for bringing it up! So, yesterday, I have uploaded my new port of YoSys to the mailing list: You can find the link to it below. As you can see, FOR NOW, I have decided to give it a rather silly name. My hope is, that somebody else will come up with a better solution, before it can truly become part of the ports tree. The way I see it, there are two options: 1. Leave the name as it is, have cad/yosys and cad/yosys-takeover in parallel. 2. Replace cad/yosys with my new version, let cad/qflow potentially break until somebody fixes it. (Also remove cad/abc along with it) My personal preference is the second one.... But, then again, I have never "updated" a port before, this is a rather new experience. An exciting one! :) Thomas -x-x-x-x-x-x-x-x-x-x-x-x-x https://marc.info/?l=openbsd-ports&m=178138632007504&w=2 (prjpeppercorn) https://marc.info/?l=openbsd-ports&m=178138505807059&w=2 (nextpnr) https://marc.info/?l=openbsd-ports&m=178138728807954&w=2 (openfpgaloader) https://marc.info/?l=openbsd-ports&m=178138490606980&w=2 (yosys-takeover) On 6/12/26 22:06, Matthias Kilian wrote: > Hi, > > [cc'd maintainer in question, just to be sure] > > On Fri, Jun 12, 2026 at 06:52:01PM +0200, Thomas Dettbarn wrote: >> I need some guidance. I was unsuccesful to contact the Maintainer >> of the ports cad/abc and cad/yosys. > Did your mails bounce? Or was there no answer? If so, for how long? > >> And now I am thinking of creating replacements. >> >> However, I am concerned that it might come of as rude, to just >> take over from him? > If his address is unreachable, or if he didn't reply within a couple > of weeks, I don't think it's rude. BTW: the last mention of him I can > see in CVSROOT/Changelog.* was 2022/12/06 (looking for just22 and > laurenzis). > >> cad/abc and cad/yosys are already part of the ports tree, but... >> they are rather outdated. > cad/qflow is also from him and looks badly outdated. And I think, > some other of his ports were mentioned in naddys amd64 lists of > ports broken on amd64 (mostly because of llvm-22). > > Ciao, > Kili >
No comments:
Post a Comment