snakes-game team mailing list archive

[Josh Brown <joshbrown15@xxxxxxxxx>]

Over the past few days, and now that we are almost ready the first
release, I've been thinking about packaging and how to go about it. Of
course we could just stick all the packaging in with the code, but I
find that leads to mistakes.

I've been thinking about using tiered branches to separate the code from
the packaging and debianization. I had something like this in mind:

  lp:~snakes/snakes/code
      ↳ lp:~snakes/snakes/pkg
            ↳ lp:~snakes/snakes/deb

Changes would be made to their relevant branches, then merged
downstream, eventually being packaged as a .deb and released.

This system would mean that you won't have to worry about packaging when
developing code, and should hopefully make things less confusing (I
frequently forget to update manifests when adding or removing files).

I'm new to the whole packaging and upstream/downstream thing, so I just
wanted an opinion on whether this is the right move to make - I don't
want to overcomplicate things.