| 1 |
On 21/03/16 00:05, Zac Medico wrote: |
| 2 |
> On 03/20/2016 11:45 PM, Andrew Udvare wrote: |
| 3 |
>> https://github.com/google/google-api-go-client/ |
| 4 |
>> |
| 5 |
>> Looking at these to generate ebuilds for (with a script and GitHub API). |
| 6 |
>> There might be an issue with assuming versions supersede (otherwise why |
| 7 |
>> would they keep multiple versions up?). |
| 8 |
> |
| 9 |
> Can you clarify which versions you're talking about? We shouldn't slot |
| 10 |
> it if the new versions are backward compatible. |
| 11 |
|
| 12 |
The version numbers are the packages like: |
| 13 |
|
| 14 |
google.golang.org/api/adexchangebuyer/v1.2 |
| 15 |
google.golang.org/api/adexchangebuyer/v1.3 |
| 16 |
google.golang.org/api/adexchangebuyer/v1.4 |
| 17 |
|
| 18 |
I was thinking to make something like: |
| 19 |
|
| 20 |
dev-go/go-google-api-adexchangebuyer1.2 |
| 21 |
dev-go/go-google-api-adexchangebuyer1.3 |
| 22 |
dev-go/go-google-api-adexchangebuyer1.4 |
| 23 |
|
| 24 |
Then of course slotting seems valid so the version suffix can go away, |
| 25 |
if these are not compatible. |
| 26 |
|
| 27 |
> Only slot if the new version is not backward compatible. |
| 28 |
|
| 29 |
I agree on this slotting policy. It definitely is a bit hard to tell if |
| 30 |
they are backward compatible in an automated fashion. |
| 31 |
|
| 32 |
I think these may be compatible in many cases, however even though some |
| 33 |
things may remain the same between versions, the API endpoint changes |
| 34 |
with these numbers. It is hard to figure out compatibility and I think |
| 35 |
the general assumption by developers is none. |
| 36 |
|
| 37 |
>> Currently I'm re-wrapping https://github.com/odeke-em/drive (I had done |
| 38 |
>> this before when there were no Go helper eclasses). |
| 39 |
> |
| 40 |
> Oh, that could be handy for drive users. |
| 41 |
> |
| 42 |
It's a decent alternative to what was Grive. Although I have only |
| 43 |
learned recently of the fork to fix Grive for the newer APIs (already on |
| 44 |
Portage). |
| 45 |
|
| 46 |
The other option on building Drive is to emulate `go get` (put itself |
| 47 |
and all deps in SRC_URI and fix up a GOROOT to compile with). Some |
| 48 |
packages already do this partially, like go-oauth2 which grabs other |
| 49 |
things in SRC_URI that could be separated out. |
| 50 |
|
| 51 |
Go is nice, but is difficult to package. |
| 52 |
|
| 53 |
Andrew |
Archives