Re: GitHub muesli/beehive porting efforts

2019-05-18 Thread Landry Breuil
On Sat, May 18, 2019 at 09:39:47AM -0400, Antoine Jacoutot wrote: > I talking about this: https://golang.org/cmd/go/#hdr-Vendor_Directories > > Usually go softwares require a particular version of their dependencies and > this isn’t really manageable in ports where it a common dependencies may b

Re: GitHub muesli/beehive porting efforts

2019-05-18 Thread Antoine Jacoutot
I talking about this: https://golang.org/cmd/go/#hdr-Vendor_Directories Usually go softwares require a particular version of their dependencies and this isn’t really manageable in ports where it a common dependencies may be required by some go ports but with a different version. — Antoine >

Re: GitHub muesli/beehive porting efforts

2019-05-18 Thread J Sisson
If you mean setting a separate directory as the GO_ROOT for third party packages and whatnot, certainly. I was under the impression that ports were preferred, though, based on reading ports@ emails about go projects. Did I misunderstand? Jonathon On Sat, May 18, 2019, 08:29 Antoine Jacoutot wro

Re: GitHub muesli/beehive porting efforts

2019-05-18 Thread Antoine Jacoutot
Can’t they use a vendor directory instead of having to ship all dependencies ? — Antoine > On 18 May 2019, at 08:00, J Sisson wrote: > > Hey ports, > > I'm working on a port for github/muesli/beehive, "an event and agent > system, which allows you to create your own agents that perform > auto

GitHub muesli/beehive porting efforts

2019-05-18 Thread J Sisson
Hey ports, I'm working on a port for github/muesli/beehive, "an event and agent system, which allows you to create your own agents that perform automated tasks triggered by events and filters." it's a pretty neat system that can automate a lot of tasks, and I've been working with upstream to get