From: Aloz1 <Aloz1@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: yosys: update to 0.47.
Date: Mon, 11 Nov 2024 22:35:55 +0100 [thread overview]
Message-ID: <20241111213555.9BFA8250BE@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52979@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
New comment by Aloz1 on void-packages repository
https://github.com/void-linux/void-packages/pull/52979#issuecomment-2469063783
Comment:
Had a chat with the upstream yosys devs. They strongly advised that the yosys package switch to using yosys-abc instead of berkely-abc. Hold off on merging this for now. I'll update to include a new yosys-abc package.
Thoughts on what to do with berkely-abc? yosys is the only package that depends on it (according to xbps-query -X). Should we leave it in? Or just remove it?
prev parent reply other threads:[~2024-11-11 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 2:09 [PR PATCH] " Aloz1
2024-11-10 3:08 ` [PR PATCH] [Updated] " Aloz1
2024-11-11 21:34 ` Aloz1
2024-11-11 21:35 ` Aloz1
2024-11-11 21:35 ` Aloz1 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241111213555.9BFA8250BE@inbox.vuxu.org \
--to=aloz1@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).