On 12 June 2015 at 13:49, William Hubbs wrote:
> Does anyone know how third party go packages are being handled on other
> distros?
In Debian at least, each Go package is being packaged individually
(using version numbers where possible, but otherwise using fun
0.0~gitMMDD.1.GITHASH construct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/12/2015 10:49 PM, William Hubbs wrote:
> On Fri, Jun 12, 2015 at 10:02:41PM +0200, Kristian Fiskerstrand
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>
...
>>
>> That said, I understand the structure. I don't like it, but
On Fri, Jun 12, 2015 at 10:02:41PM +0200, Kristian Fiskerstrand wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 06/12/2015 09:58 PM, William Hubbs wrote:
> > On Fri, Jun 12, 2015 at 11:18:29AM -0700, Patrick McLean wrote:
> >> On Fri, 12 Jun 2015 12:54:04 -0500 William Hubbs
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/12/2015 09:58 PM, William Hubbs wrote:
> On Fri, Jun 12, 2015 at 11:18:29AM -0700, Patrick McLean wrote:
>> On Fri, 12 Jun 2015 12:54:04 -0500 William Hubbs
>> wrote:
..
> Since the Go compiler bundles all the necessary packages to compile
On Fri, Jun 12, 2015 at 11:18:29AM -0700, Patrick McLean wrote:
> On Fri, 12 Jun 2015 12:54:04 -0500
> William Hubbs wrote:
>
> > All,
> >
> > in looking at some of the Go ebuilds we have in the tree, I see that
> > some of them, for example go-tools, have multiple Go packages in a
> > single re
On Fri, 12 Jun 2015 12:54:04 -0500
William Hubbs wrote:
> All,
>
> in looking at some of the Go ebuilds we have in the tree, I see that
> some of them, for example go-tools, have multiple Go packages in a
> single repository. This means that something like:
>
> go get -d -u -t golang.org/x/tool
All,
in looking at some of the Go ebuilds we have in the tree, I see that
some of them, for example go-tools, have multiple Go packages in a
single repository. This means that something like:
go get -d -u -t golang.org/x/tools
will fail. There is an issue opened upstream about this [1].
My ques
