[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC 0/4] Getting rid of input labels?
From: |
Maxime Devos |
Subject: |
Re: [PATCH RFC 0/4] Getting rid of input labels? |
Date: |
Thu, 27 May 2021 21:02:52 +0200 |
User-agent: |
Evolution 3.34.2 |
Ludovic Courtès schreef op wo 26-05-2021 om 15:43 [+0200]:
> Hi Maxime,
>[...]
> In many cases, you don’t need the ability to refer to a specific input;
> you just need all the inputs to contribute to search path environment
> variables, and that’s enough. A “label collision” does not matter at
> all in this case.
>
> In some cases, you do need to refer to a specific input, as in:
>
> [...]
> In this case, there are now two options:
>
> 1. Arrange so that label is unique among your inputs, as is already
> the case.
>
> 2. [...]
>
> Do you think there are unaddressed issues with go-ipfs-migrations?
As long as there remains a possibility of overriding the ‘default‘ label
generated from the package name, then everything seems ok for the
(not-yet-packaged) go-ipfs-migrations. This appears to remain the case,
so ok?
Greetings,
Maxime.
signature.asc
Description: This is a digitally signed message part
- [PATCH RFC 0/4] Getting rid of input labels?, Ludovic Courtès, 2021/05/20
- [PATCH RFC 2/4] DRAFT packages: Allow inputs to be plain package lists., Ludovic Courtès, 2021/05/20
- [PATCH RFC 1/4] records: Support field sanitizers., Ludovic Courtès, 2021/05/20
- [PATCH RFC 3/4] DRAFT gnu: Change inputs of core packages to plain lists., Ludovic Courtès, 2021/05/20
- [PATCH RFC 4/4] DRAFT lint: Add 'input-labels' checker., Ludovic Courtès, 2021/05/20
- Re: [PATCH RFC 0/4] Getting rid of input labels?, Vincent Legoll, 2021/05/20
- Re: [PATCH RFC 0/4] Getting rid of input labels?, Maxime Devos, 2021/05/20
- Re: [PATCH RFC 0/4] Getting rid of input labels?, Nicolas Goaziou, 2021/05/21