Package Details: qucsator 0.0.20-1

Git Clone URL: https://aur.archlinux.org/qucsator.git (read-only, click to copy)
Package Base: qucsator
Description: An integrated circuit simulator
Upstream URL: http://qucs.sourceforge.net
Licenses: GPL
Submitter: d_adler
Maintainer: d_adler
Last Packager: d_adler
Votes: 1
Popularity: 0.000002
First Submitted: 2021-01-06 10:49 (UTC)
Last Updated: 2021-01-06 10:49 (UTC)

Latest Comments

felixs commented on 2022-11-16 13:42 (UTC)

Hi dreieck -- Thanks for looking into this.

Qucsator is part of the Qucs project, and is contained in the qucs package for historical reasons. It should be a dependency or recommend instead.

Technically, qucsator-0.0.20 conflicts with qucs <0.0.20, but qucs 0.0.20 has not been released yet.

What we need is a qucs package without qucsator. There is some preliminary work on this [1]. We'd need to move on and make the release... See also my december comment on qucs-0.0.20-rc2 [2].

[1] https://github.com/Qucs/qucs/tree/develop_filtered [2] https://aur.archlinux.org/packages/qucs

dreieck commented on 2022-11-16 12:52 (UTC)

How does this relate with the package qucs?

Do you need to add conflicts=(qucs) and provides=("qucs=${pkgver}")?

Regards!

felixs commented on 2021-11-11 15:55 (UTC)

There is an issue with parallel builds reported twice [1], issue #10 and #17. From what I remember, this is real, and it is certainly a race condition and shows up irregularly. I don't believe it has been fixed. It should be analysed & worked at upstream. Please stick to -j1 until this has been resolved.

Thanks.

[1] https://github.com/Qucs/qucsator/issues?q=parallel

shuyuan-liu commented on 2021-11-08 10:50 (UTC)

Thanks @d_adler for the package, builds fine on my system. One problem is that this PKGBUILD insists on using a single CPU core (make -j1), overriding the user's settings in /etc/makepkg.conf. I tried cloning 0.0.20 from GitHub and building with make -j8, it went fine and was a lot faster. Is there a reason why you decided to force using 1 CPU only? Also the PKGBUILD doesn't verify the files downloaded; usually this is only done for a "-git" package where the file could frequently change. For a stable version package, most PKGBUILDs I've seen download the source as a .tar.gz file, whose checksum can be verified.