Hi Wael,
I am curious if the approach outlined in this branch of the thread has
continued to work for you so far, vs. perhaps you hit a snag after the
initial success you reported below?
Regards,
thepudds
On Wednesday, March 13, 2019 at 2:46:59 PM UTC-4, Wael Nasreddine wrote:
>
> On Monday, M
On Thursday, March 14, 2019 at 6:52:52 AM UTC+1, Wael Nasreddine wrote:
>
> I'm going to describe how I ended up packaging the go modules (and so far
> it seems to work correctly). I have also replied inline below
>
> I'm using a two-phase approach to package Go modules for Nix:
>
>1. During t
I'm going to describe how I ended up packaging the go modules (and so far
it seems to work correctly). I have also replied inline below
I'm using a two-phase approach to package Go modules for Nix:
1. During the first phase, a package named after the module with the
suffix *-go-modules* i
On Wednesday, March 13, 2019 at 7:25:35 PM UTC+1, Wael Nasreddine wrote:
>
> On Monday, March 11, 2019 at 10:01:04 AM UTC-7, Manlio Perillo wrote:
>>
>> Do you perhaps have the same requirements as in the thread
>> https://groups.google.com/forum/#!topic/golang-dev/DD88cds-LuI
>> as reported by Nic
On Wednesday, March 13, 2019 at 7:25:35 PM UTC+1, Wael Nasreddine wrote:
>
> On Monday, March 11, 2019 at 10:01:04 AM UTC-7, Manlio Perillo wrote:
>>
>> Do you perhaps have the same requirements as in the thread
>> https://groups.google.com/forum/#!topic/golang-dev/DD88cds-LuI
>> as reported by Nic
On Monday, March 11, 2019 at 12:33:29 PM UTC-7, thepud...@gmail.com wrote:
>
> Hi Wael,
>
> Sorry, I am not quite following what you have and have not tried yet, and
> which issues you have hit with which techniques.
>
No worries, I'll try to address your questions to clarify the issues I'm
havi
On Monday, March 11, 2019 at 10:01:04 AM UTC-7, Manlio Perillo wrote:
>
> Do you perhaps have the same requirements as in the thread
> https://groups.google.com/forum/#!topic/golang-dev/DD88cds-LuI
> as reported by Nicolas Mailhot?
>
> That is, you need to patch the upstream source but keep the sam
Hi Wael,
Sorry, I am not quite following what you have and have not tried yet, and
which issues you have hit with which techniques.
Is one of the issues that the 'vcs' cache directory changes, even if the
actual code you need for your build has not changed?
If so, I wonder if you might be able
On Monday, March 11, 2019 at 4:22:04 PM UTC+1, Wael Nasreddine wrote:
> [...]
> On Sunday, March 10, 2019 at 6:59:07 PM UTC-7, Manlio Perillo wrote:
On Monday, March 11, 2019 at 12:30:02 AM UTC+1, Wael Nasreddine wrote:
>
> TL;DR Given a Go module, assuming that I have already
On Mon, Mar 11, 2019 at 3:02 AM Manlio Perillo
wrote:
> On Monday, March 11, 2019 at 6:12:05 AM UTC+1, Wael Nasreddine wrote:
>>
>> On Sunday, March 10, 2019 at 6:44:10 PM UTC-7, Manlio Perillo wrote:
>>>
>>> On Monday, March 11, 2019 at 2:06:44 AM UTC+1, Wael Nasreddine wrote:
>>>
On Monday, March 11, 2019 at 6:12:05 AM UTC+1, Wael Nasreddine wrote:
>
> On Sunday, March 10, 2019 at 6:44:10 PM UTC-7, Manlio Perillo wrote:
>>
>> On Monday, March 11, 2019 at 2:06:44 AM UTC+1, Wael Nasreddine wrote:
>>>
>>>
>>>
>>> On Sunday, March 10, 2019 at 5:01:01 PM UTC-7, Manlio Perillo wr
On Sunday, March 10, 2019 at 5:01:01 PM UTC-7, Manlio Perillo wrote:
>
> On Monday, March 11, 2019 at 12:30:02 AM UTC+1, Wael Nasreddine wrote:
>>
>> TL;DR Given a Go module, assuming that I have already done `go mod
>> download`: Is it possible to prevent network access if I delete the entire
>>
On Sunday, March 10, 2019 at 6:44:10 PM UTC-7, Manlio Perillo wrote:
>
> On Monday, March 11, 2019 at 2:06:44 AM UTC+1, Wael Nasreddine wrote:
>>
>>
>>
>> On Sunday, March 10, 2019 at 5:01:01 PM UTC-7, Manlio Perillo wrote:
>>>
>>> On Monday, March 11, 2019 at 12:30:02 AM UTC+1, Wael Nasreddine wro
On Monday, March 11, 2019 at 12:30:02 AM UTC+1, Wael Nasreddine wrote:
>
> TL;DR Given a Go module, assuming that I have already done `go mod
> download`: Is it possible to prevent network access if I delete the entire
> `$GOPATH/pkg/mod/cache`?
>
>
Another solution is to delete only $GOPATH/pkg/
On Monday, March 11, 2019 at 2:06:44 AM UTC+1, Wael Nasreddine wrote:
>
>
>
> On Sunday, March 10, 2019 at 5:01:01 PM UTC-7, Manlio Perillo wrote:
>>
>> On Monday, March 11, 2019 at 12:30:02 AM UTC+1, Wael Nasreddine wrote:
>>>
>>> TL;DR Given a Go module, assuming that I have already done `go mod
On Sunday, March 10, 2019 at 5:01:01 PM UTC-7, Manlio Perillo wrote:
>
> On Monday, March 11, 2019 at 12:30:02 AM UTC+1, Wael Nasreddine wrote:
>>
>> TL;DR Given a Go module, assuming that I have already done `go mod
>> download`: Is it possible to prevent network access if I delete the entire
On Monday, March 11, 2019 at 12:30:02 AM UTC+1, Wael Nasreddine wrote:
>
> TL;DR Given a Go module, assuming that I have already done `go mod
> download`: Is it possible to prevent network access if I delete the entire
> `$GOPATH/pkg/mod/cache`?
>
>
Yes. Use `go mod vendor` and the -mod=vendor b
17 matches
Mail list logo
