Can you please add configure options "enable-ktls" and "enable-ec_nistp_64_gcc_128" as per the standard openssl package? Thanks!
OK, done.
Git Clone URL: | https://aur.archlinux.org/openssl-git.git (read-only, click to copy) |
---|---|
Package Base: | openssl-git |
Description: | Toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols |
Upstream URL: | https://www.openssl.org/ |
Licenses: | Apache-2.0 |
Conflicts: | openssl |
Provides: | libcrypto.so, libssl.so, openssl |
Submitter: | EndlessEden |
Maintainer: | Chocobo1 |
Last Packager: | Chocobo1 |
Votes: | 2 |
Popularity: | 0.000000 |
First Submitted: | 2017-07-13 03:55 (UTC) |
Last Updated: | 2025-02-24 06:50 (UTC) |
Can you please add configure options "enable-ktls" and "enable-ec_nistp_64_gcc_128" as per the standard openssl package? Thanks!
OK, done.
Can you please add configure options "enable-ktls" and "enable-ec_nistp_64_gcc_128" as per the standard openssl package? Thanks!
Before you flag this package outdated, read this: An VCS package is never outdated!! (unless it won't build or have other issues)
From https://wiki.archlinux.org/title/PKGBUILD#pkgver:
makepkg can automatically update this variable by defining a pkgver() function in the PKGBUILD.
It means that this package will try to automatically update itself to the latest version every time you build it.
It worked now. Thanks for quick fixing!
How is this package meant to be uses as installing it now it seems to replace the system's openssl dependencies?
Yes, it is intended for user (or really the developers) to test the bleeding edge version. So be careful when deploying it on production machine/environment.
Is it possible to use this package as a drop-in replacement of the default package?
I pushed another fix, it should be ok now.
Cool, thanks for quick fix.
How is this package meant to be uses as installing it now it seems to replace the system's openssl dependencies?
:: openssl-git and openssl are in conflict. Remove openssl? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing openssl breaks dependency 'libcrypto.so=3-64' required by libarchive
:: removing openssl breaks dependency 'libcrypto.so=3-64' required by ostree
:: removing openssl breaks dependency 'libcrypto.so=3-64' required by sudo
:: removing openssl breaks dependency 'libssl.so=3-64' required by sudo
:: removing openssl breaks dependency 'libcrypto.so=3-64' required by systemd
:: removing openssl breaks dependency 'libssl.so=3-64' required by systemd
-> exit status 1
Is it possible to use this package as a drop-in replacement of the default package?
==> ERROR: pkgver() generated an invalid version: 3.1.0-beta1.r2065.g43a9e682d8
Fixed.
==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 3.1.0-beta1.r2065.g43a9e682d8
-> error making: openssl-git
yay openssl-g 35.04s user 4.27s system 107% cpu 36.552 total
In prepare(), patch -Np0 ... should be patch -Np1 ...
Fixed, thanks!
In prepare()
, patch -Np0 ...
should be patch -Np1 ...
Pinned Comments
Chocobo1 commented on 2023-09-08 10:41 (UTC)
Before you flag this package outdated, read this: An VCS package is never outdated!! (unless it won't build or have other issues)
From https://wiki.archlinux.org/title/PKGBUILD#pkgver:
It means that this package will try to automatically update itself to the latest version every time you build it.
Also see: https://wiki.archlinux.org/title/Arch_User_Repository#What_is_the_difference_between_foo_and_foo-git_packages?