From: mtboehlke <mtboehlke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ngspice: update to 35 and fix issue with binary not built/installed
Date: Thu, 26 Aug 2021 07:00:08 +0200 [thread overview]
Message-ID: <20210826050008.wbGvPuS1nMENPBgMyLD2wnXckFXXetADdRfXKZmiPvo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32403@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
New comment by mtboehlke on void-packages repository
https://github.com/void-linux/void-packages/pull/32403#issuecomment-905679970
Comment:
@ericonr I am not a KiCad user ( or even really an ngspice user), but I was curious about the `/usr/lib/ngspice/*cm` files. It appears that they are code models used by the xspice extension. They can be used from KiCad, and should be made available, which this PR would break right now. My question is how best to handle that. Should they be moved to libngspice and have ngspice then depend on it as well, make another subpackage called something like ngspice-common, or maybe not split off libngspice at all? (PR reflects first option)
next prev parent reply other threads:[~2021-08-26 5:00 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 22:57 [PR PATCH] ngspice: update to 34 mtboehlke
2021-08-07 23:04 ` mtboehlke
2021-08-07 23:05 ` mtboehlke
2021-08-07 23:10 ` [PR PATCH] [Updated] " mtboehlke
2021-08-07 23:13 ` mtboehlke
2021-08-09 17:20 ` [PR REVIEW] " ericonr
2021-08-09 17:20 ` ericonr
2021-08-09 17:20 ` ericonr
2021-08-09 17:20 ` ericonr
2021-08-09 19:01 ` [PR PATCH] [Updated] " mtboehlke
2021-08-10 16:45 ` mtboehlke
2021-08-10 16:49 ` [PR REVIEW] " mtboehlke
2021-08-10 16:49 ` mtboehlke
2021-08-10 16:50 ` [PR REVIEW] " mtboehlke
2021-08-10 16:50 ` mtboehlke
2021-08-10 17:07 ` ericonr
2021-08-10 19:46 ` mtboehlke
2021-08-11 1:39 ` ericonr
2021-08-11 16:57 ` [PR PATCH] [Updated] " mtboehlke
2021-08-11 17:05 ` ngspice: update to 35 mtboehlke
2021-08-11 17:07 ` mtboehlke
2021-08-12 1:07 ` [PR REVIEW] " ericonr
2021-08-12 1:07 ` ericonr
2021-08-12 1:07 ` ericonr
2021-08-12 2:28 ` [PR PATCH] [Updated] " mtboehlke
2021-08-12 2:29 ` mtboehlke
2021-08-12 2:29 ` mtboehlke
2021-08-12 2:53 ` mtboehlke
2021-08-12 2:56 ` [PR REVIEW] " mtboehlke
2021-08-12 3:02 ` mtboehlke
2021-08-12 3:07 ` [PR REVIEW] " sgn
2021-08-12 3:07 ` sgn
2021-08-12 3:26 ` mtboehlke
2021-08-12 3:29 ` mtboehlke
2021-08-12 23:53 ` [PR PATCH] [Updated] " mtboehlke
2021-08-12 23:55 ` [PR REVIEW] " mtboehlke
2021-08-16 15:06 ` mtboehlke
2021-08-16 15:07 ` mtboehlke
2021-08-17 16:15 ` [PR PATCH] [Updated] " mtboehlke
2021-08-17 16:19 ` mtboehlke
2021-08-25 16:17 ` ngspice: update to 35 and fix issue with binary not built/installed mtboehlke
2021-08-25 16:17 ` mtboehlke
2021-08-26 4:24 ` [PR PATCH] [Updated] [WIP] " mtboehlke
2021-08-26 4:27 ` mtboehlke
2021-08-26 5:00 ` mtboehlke [this message]
2021-08-29 19:49 ` ericonr
2021-08-29 19:50 ` ericonr
2021-08-30 0:12 ` [PR PATCH] [Updated] " mtboehlke
2021-08-30 0:44 ` mtboehlke
2021-08-30 3:54 ` ericonr
2021-08-30 5:01 ` mtboehlke
2021-08-30 13:00 ` ericonr
2021-08-30 13:30 ` [PR PATCH] [Updated] " ericonr
2021-08-30 13:31 ` [PR PATCH] [Merged]: " ericonr
2021-08-30 13:31 ` ericonr
2021-08-30 15:25 ` mtboehlke
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=20210826050008.wbGvPuS1nMENPBgMyLD2wnXckFXXetADdRfXKZmiPvo@z \
--to=mtboehlke@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).