[pkg-go] Why should packaging be distant from upstream code?

Ximin Luo infinity0 at pwned.gg
Fri May 23 17:18:25 UTC 2014

On 23/05/14 17:49, Joseph Anthony Pasquale Holsten wrote:
> I’m working on packaging for chef-golang, and stapleberg informed me that recommendation is to store the deb packaging be in a separate repo from the upstream code. What’s the reasoning?
> The work is happening here: https://github.com/marpaia/chef-golang/pull/33

If upstream and debian packaging is maintained by separate teams, arranging access rights is easier. You don't want to have to get upstream's approval every time you want to do a debian packaging change. Especially if the thing is team-maintained, and several people could want to edit the debian packaging.

If they are the same person, it's less important. However, a clearer separation is still good to reduce clutter on both sides. Upstream typically doesn't care about the details of debian changes, and vice versa, and seeing both in the same history graph can be too much information.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 880 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20140523/5c225e3d/attachment.sig>

More information about the Pkg-go-maintainers mailing list