Search Criteria
Package Details: pothos 0.7.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/pothos.git (read-only, click to copy) |
---|---|
Package Base: | pothos |
Description: | The Pothos data-flow framework |
Upstream URL: | https://github.com/pothosware/PothosCore/wiki |
Licenses: | boost |
Submitter: | eduardosm |
Maintainer: | None |
Last Packager: | eduardosm |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2017-12-26 13:43 (UTC) |
Last Updated: | 2021-01-30 12:15 (UTC) |
Dependencies (6)
- poco (poco-gitAUR)
- portaudio
- python (python37AUR, python311AUR, python310AUR)
- soapysdr (soapysdr-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
- nlohmann-json (nlohmann-json-gitAUR) (make)
Latest Comments
eduardosm commented on 2018-06-11 09:00 (UTC)
@FFY00 You can provide patches for the PKGBUILD, I'm open to contributions
FFY00 commented on 2018-06-10 11:55 (UTC)
@eduardosm thanks for replying! The generated tarball file should always have the same checksum. If they don't, this means the release was tampered with, which is exactly what we want to check. If you want, I could try to update the PKGBUILD for you. Thanks :)
eduardosm commented on 2018-06-10 11:12 (UTC)
@FFY00 The zips and tar.gz seem to be created on the fly by github when you download them, so you can't rely on them having stable checksums. There are also git submodules that are not included in the tarballs, so it is easier to clone the repository and let git take care of them. Of course, I could make it download all the tarballs and unpacking them in the correct place, but I don't have time for that right now. Anyways, so far cloning the git repository doesn't take much time. I hope you understand.
FFY00 commented on 2018-06-10 10:23 (UTC) (edited on 2018-06-10 10:23 (UTC) by FFY00)
Hey, could you please use the release .tar.gz file instead of the git repository? There's no need to clone the whole repo. Also, by cloning the repo instead of fetching the zip file, we will ignore the checksum tests, which is obviously bad and should be avoided if possible.
Thanks :)
eduardosm commented on 2017-12-27 17:25 (UTC)
@FabioLolix I hadn't noticed it, thanks.
FabioLolix commented on 2017-12-27 00:07 (UTC)
For the license you can write 'boost' since it has became a know license or add a copy to ${pkgdir}/usr/share/licenses/${pkgname}