Michał Górny writes:
> On Wed, 2024-11-27 at 15:30 -0500, Eli Schwartz wrote:
>> The current state of verify-sig support is a bit awkward. We rely on
>> validating distfiles against a known trusted keyring, but creating the
>> known trusted keyring is basically all manual verification. We somehow
Eli Schwartz writes:
> The current state of verify-sig support is a bit awkward. We rely on
> validating distfiles against a known trusted keyring, but creating the
> known trusted keyring is basically all manual verification. We somehow
> decide an ascii armored key is good enough without any po
On Wed, 2024-11-27 at 15:30 -0500, Eli Schwartz wrote:
> The current state of verify-sig support is a bit awkward. We rely on
> validating distfiles against a known trusted keyring, but creating the
> known trusted keyring is basically all manual verification. We somehow
> decide an ascii armored k
On 11/27/24 4:57 PM, Sam James wrote:
> Eli Schwartz writes:
>> +# @EXAMPLE:
>> +# Example use:
>> +#
>> +# @CODE
>> +# SEC_KEYS_VALIDPGPKEYS=(
>> +# '4EC8A4DB7D2E01C00AF36C49E5C587B5E286C65A:jsmith:github'
>> +# )
>
> Can you expand the example(s) here maybe with some comments in the array
> t
---
eclass/cargo.eclass | 43 +++
1 file changed, 35 insertions(+), 8 deletions(-)
diff --git a/eclass/cargo.eclass b/eclass/cargo.eclass
index 95ff317e1f21..aa59d38d8600 100644
--- a/eclass/cargo.eclass
+++ b/eclass/cargo.eclass
@@ -93,6 +93,10 @@ ECARGO_V
Hi,
associative arrays declared in functions are implicitly local in bash.
That means any associative array declared in global ebuild scope needs
to be declare global explicitly, as it's not guaranteed not to be
sourced within a function by a PM ( e.g. paludis does this ).
https://lists.gnu.
The current state of verify-sig support is a bit awkward. We rely on
validating distfiles against a known trusted keyring, but creating the
known trusted keyring is basically all manual verification. We somehow
decide an ascii armored key is good enough without any portage
assistance, then arrange
Bump EAPI 7 -> 8 as required by eclass. ;)
This is a nice demonstration of using the eclass. It showcases some
advanced usage, in particular, how to augment a single key within a
keyring published on upstream's website with an extended expiration date
from the openpgp.org keyserver.
The ebuild wa
# Takuya Wakazono (2024-11-27)
# Replaced by sys-boot/woeusb-ng, which has more recent upstream
# activity and optional GUI support.
# Removal on 2024-12-24.
sys-boot/woeusb
The current state of verify-sig support is a bit awkward. We rely on
validating distfiles against a known trusted keyring, but creating the
known trusted keyring is basically all manual verification. We somehow
decide an ascii armored key is good enough without any portage
assistance, then arrange
Bump EAPI 7 -> 8 as required by eclass. ;)
This is a nice demonstration of using the eclass. It showcases some
advanced usage, in particular, how to augment a single key within a
keyring published on upstream's website with an extended expiration date
from the openpgp.org keyserver.
The ebuild wa
v2 changes:
- add src_test
- add support for gentoo keyserver
- fix small typo in handling multiple sources
- remove outdated die based on review
Eli Schwartz (2):
sec-keys.eclass: new eclass
sec-keys/openpgp-keys-gnutls: update to use sec-keys.eclass
eclass/sec-keys.eclass
On 11/27/24 4:12 PM, Michał Górny wrote:
> On Wed, 2024-11-27 at 15:30 -0500, Eli Schwartz wrote:
>> The current state of verify-sig support is a bit awkward. We rely on
>> validating distfiles against a known trusted keyring, but creating the
>> known trusted keyring is basically all manual verifi
On 24/11/2024 13.24, Ulrich Müller wrote:
This implements a pipestatus command, as discussed in bug 566342 [1]
and on IRC.
Subject to approval by the council, the command would be added in
EAPI 9. Its definition in the Package Manager Specification would be
along the lines of:
╓
║ Tests the
On Wed, 2024-11-27 at 11:41 +0100, Florian Schmaus wrote:
> I looked forward to use pipestatus() in texlive-modules.eclass [1], but
> since the pipe includes a 'grep', which is not uncommon, I can not use
> what is currently proposed.
Use sed instead.
--
Best regards,
Michał Górny
signature
> On Wed, 27 Nov 2024, Florian Schmaus wrote:
>> ╓
>> ║ Tests the shell's pipe status array, i.e. the exit status of the
>> ║ command(s) in the most recently executed foreground pipeline.
>> ║ Returns shell true (0) if all elements are zero, or the last
>> ║ non-zero element otherwise. If
16 matches
Mail list logo
