well an issue <https://github.com/golang/go/issues/44840> was filed, and
promptly closed.

On Sun, Mar 7, 2021 at 6:36 AM James Lawrence <jljat...@gmail.com> wrote:

> I read through those issues Paul, I found them less than convincing for
> the global go install use case. regardless I'll file an issue. I didn't
> want to file an issue because of how long and pointless most of the
> conversation around the global install replace directive usage seemed.
>
> I'll file other issues around the random set of related irritations the
> ongoing module work has caused.
>
> On Sun, Mar 7, 2021 at 5:59 AM 'Axel Wagner' via golang-nuts <
> golang-nuts@googlegroups.com> wrote:
>
>> I wasn't aware that this restriction is intentional. I wasn't part of
>> that discussion and it seems too long for me to read after the fact, so I
>> probably shouldn't comment on it. I'm admittedly a bit befuddled by the
>> design decisions, though (as I understand them).
>>
>> On Sun, Mar 7, 2021 at 8:57 AM Paul Jolly <p...@myitcv.io> wrote:
>>
>>> >> I missed the conversation originally. however go install has been
>>> left in a unfortunate state where it bewilderingly errors out when the main
>>> module contains a replace directive.
>>> >
>>> > This sounds like a bug. I would file an issue with an easy
>>> reproduction case.
>>>
>>> Erroring on replace directives is an intentional decision for now:
>>> https://github.com/golang/go/issues/40276#issue-659471259
>>>
>>> But might be relaxed in the future:
>>>
>>> > Parts of this proposal are more strict than is technically necessary
>>> (for
>>> > example, requiring one module, forbidding replace directives). We
>>> could relax
>>> > these restrictions without breaking compatibility in the future if it
>>> seems
>>> > expedient. It would be much harder to add restrictions later.
>>>
>>> If you think this is a valid case for requiring non-directory replace
>>> directives to be applied, then I suggest raising an issue with some
>>> details.
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "golang-nuts" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/golang-nuts/10AJZaH9OFU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> golang-nuts+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/golang-nuts/CAEkBMfGwcwp3if-zgQYN3HL5c%2BPedafuS6uz%2BtPBymHasFSzyw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/golang-nuts/CAEkBMfGwcwp3if-zgQYN3HL5c%2BPedafuS6uz%2BtPBymHasFSzyw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> James Lawrence
>


-- 
James Lawrence

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CALOHWHUQzZ%3DVsV%2B0ehzL90ZnchDq5tpwWOf2CMPF48e1D1v%3Dpw%40mail.gmail.com.

Reply via email to