[pkg-lxc-devel] Bug#768073: Bug#768073: LXD packaging (and lxc-go plus a little bit of salsa)
Clément Hermann
nodens at nodens.org
Sat Feb 3 15:52:28 UTC 2018
Hi,
I've resumed active work on LXD, the last dependency
(golang-gopkg-lxc-go-lxc.v2 - #883488) is almost done (pending review
and upload).
Regarding lxc-go, I suggest we archive the previous attemps, since it
will live in pkg-go repository (using gitlab Archive feature on Salsa).
Same for the lxd ubuntu package that has been imported: I think it will
be much easier to create a new package from scratch using
dh-make-golang. Of course, I intent to cherry-pick bits of Ubuntu
packaging where it makes sense.
Speaking of Salsa, can someone grant me access to lxc-team ?
on LXD packaging per se, the only difference with other go packages will
probably be that pkg-go team switched to a workflow without pristine-tar
(see https://pkg-go.alioth.debian.org/workflow-changes.html if you're
interested). And, of course, that the repo is in lxc-team namespace.
Is there anything regarding lxc-team packaging style/workflow I should
be aware of? From what I saw, the workflow seems to be using gbp with
pristine star branch, UNRELEASED target distribution until the package
is ready to upload, so very similar to what I'm used to in pkg-perl.
Please correct me if I'm wrong! :)
Cheers.
--
nodens
More information about the Pkg-lxc-devel
mailing list