> As an example, look at the cargo and cargo_fetch port groups that
implement dependencies for rust this way
Mojca suggested essentially the same thing to me off-list.
> The peco port is already using this approach and I think it is the right
way to go foward. The snippets from that port should b
On 2018-09-04 11:54, Mojca Miklavec wrote:
> Our current support for go-based software and libraries is pretty much
> non-existant. The fact that everything needs to be done manually is
> super suboptimal. Ideally we would have a PortGroup which could take
> care of dependencies in a similar way as
Hi Mojca. Thanks for the info.
> But the main question boils down to: assuming that one dependency (of
> dashing, let's say) gets updated tomorrow. Will the resulting binary
> still be the same if you rebuild it the day after tomorrow?
In the presence of a glide.lock file, it appears the answer i
On Tue, 4 Sep 2018 at 10:16, Aaron Madlon-Kay wrote:
>
> I have created a portfile for a tool written in golang:
> https://github.com/amake/macports-ports/blob/dashing/textproc/dashing/Portfile
>
> I was lazy and used glide (a golang package manager, which we have a port
> for) to grab the depende
I have created a portfile for a tool written in golang:
https://github.com/amake/macports-ports/blob/dashing/textproc/dashing/Portfile
I was lazy and used glide (a golang package manager, which we have a port
for) to grab the dependencies.
I note that no other golang port seems to use glide; furt
