[pkg-go] GitLab CI: git-buildpackage and ratt

[Martín Ferrari]

Hi,

On 19/02/18 17:13, Michael Stapelberg wrote:

> I see the role of the CI setup as complementary: I expect that people
> will still build packages locally as they work on the packages. That
> path will continue to cover the debian/* part of the package. The
> remainder (fit into the archive) will be covered by the CI. In the worst
> case, the issue will be caught on the buildds (provided one uses
> source-only uploads).

OK, good point.

> Regarding the amount of work required to make packages buildable
> directly with the Go tool, have a look at the examples I listed at the
> bottom of the document. I don’t expect to spend more than 15 minutes per
> package, and I can volunteer to do the initial fixes. We need to be on
> the same page regarding the longer-term strategy, though, otherwise
> packages will degrade quickly.
> 
> Does that address your concern?

More or less, there are things that would be very clumsy to do without a
Makefile. For example, arch-specific build tags, if you don't evaluate
the complete makefile you won't get those. Granted, if you are only
using amd64 this would be a non-issue most of the time, although you
have things like this that will still require evaluating properly
debian/rules:

export DH_GOLANG_INSTALL_EXTRA := godoc/static \
    $(wildcard */*/testdata) $(wildcard */*/*/testdata)

Dunno, seems it could work as you propose it, but at the same time I am
a bit worried that we will need to be careful not to break the system,
and that it will not be obvious when building locally.

-- 
Martín Ferrari (Tincho)