Search Criteria
Package Details: hydroxide 0.2.24-4
Git Clone URL: | https://aur.archlinux.org/hydroxide.git (read-only, click to copy) |
---|---|
Package Base: | hydroxide |
Description: | A third-party, open-source ProtonMail CardDAV, IMAP and SMTP bridge |
Upstream URL: | https://github.com/emersion/hydroxide |
Keywords: | carddav go imap protonmail protonmail-bridge smtp |
Licenses: | MIT |
Submitter: | arnottcr |
Maintainer: | arnottcr (Stetsed) |
Last Packager: | Stetsed |
Votes: | 13 |
Popularity: | 0.103510 |
First Submitted: | 2020-01-04 21:41 (UTC) |
Last Updated: | 2022-09-06 08:40 (UTC) |
Latest Comments
1 2 Next › Last »
Ranguvar commented on 2022-05-11 03:42 (UTC)
Please consider adding options=(!lto).
Some packages in core repos already do, for the benefit of users who have LTO enabled globally.
This package fails to build with LTO enabled.
tam1m commented on 2021-11-29 09:51 (UTC) (edited on 2021-11-29 10:02 (UTC) by tam1m)
Edit:
Don't really get whats happening. https://aur.archlinux.org/packages/hydroxide-git builds fine with my default config including lto.
These are my flags
CFLAGS="-march=native -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection"
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS
Could you add
options=('!lto')
?Build breaks for me with lto enabled
rEnr3n commented on 2021-10-10 01:54 (UTC)
You need to import the dev's key.
gpg --recv-keys 34FF9526CFEF0E97A340E2E40FDE7BE0E88F5E48
djdeets commented on 2021-10-09 21:33 (UTC)
For me Hydroxide fails to build with the error:
Ranguvar commented on 2021-08-27 01:52 (UTC)
Please consider adding options=(!lto) as some packages in core repos already do, for the benefit of users who have LTO enabled globally.
This package fails to build with LTO enabled.
Ultracoolguy commented on 2021-06-08 18:06 (UTC)
So I noticed the package was flagged out of date, so I went ahead and updated it. Note that I removed the .sig and the pgp key because the former had expired.
If you need help with something else let me know.
commented on 2020-04-29 08:56 (UTC)
Thanks! If you have any questions about the changes feel free to ask.
arnottcr commented on 2020-04-29 03:48 (UTC)
You seem interested and aware of community standards, happy to hand share management and let you push best practices. Added you as a Co-Maintainer, so feel free to realign things as appropriate.
commented on 2020-04-29 03:31 (UTC)
The tarball already contains a go.sum file. It will always be the same as the one that you had when committing the package since we're checking the checksum of the tarball.
More info: Go package guidelines#Modern Go project (for Go >=1.11)
Building towards
go-pie
should be preferred for security reasons. I haven't encountered any issues with building againstgo-pie
and when I tried hydroxide out everything seemed to be working as intended.More info: Go package guidelines#Building
The reason you don't see the sample PKGBUILDs copying the license is that the license is
GPL
and it's already located at/usr/share/licenses/common/GPL/license.txt
. MIT is treated as a common license, but technically each one is a different license due to theCopyright [...]
line being included, which is why you have to copy it.More info: PKGBUILD#license
I suggest you take a look at the following ArchWiki pages when you have time:
commented on 2020-04-29 03:31 (UTC)
The tarball already contains a go.sum file. It will always be the same as the one that you had when committing the package since we're checking the checksum of the tarball.
More info: Go package guidelines#Modern Go project (for Go >=1.11)
Building towards
go-pie
should be preferred for security reasons. I haven't encountered any issues with building againstgo-pie
and when I tried hydroxide out everything seemed to be working as intended.More info: Go package guidelines#Building
The reason you don't see the sample PKGBUILDs copying the license is that the license is
GPL
and it's already located at/usr/share/licenses/common/GPL/license.txt
. MIT is treated as a common license, but technically each one is a different license due to theCopyright [...]
line being included, which is why you have to copy it.More info: PKGBUILD#license
I suggest you take a look at the following ArchWiki pages when you have time:
1 2 Next › Last »