Re: Self-maintained Debian packages best practice
- To: debian-mentors@lists.debian.org
- Subject: Re: Self-maintained Debian packages best practice
- From: Russ Allbery <rra@debian.org>
- Date: Sun, 30 Nov 2014 18:45:52 -0800
- Message-id: <[🔎] 87mw78t7dr.fsf@hope.eyrie.org>
- In-reply-to: <m5fusq$hfd$2@ger.gmane.org> (T. o. n. g.'s message of "Sun, 30 Nov 2014 20:32:26 +0000 (UTC)")
- References: <m5f896$hfd$1@ger.gmane.org> <m3tx1ghfj2.fsf@neo.luffy.cx> <20141130171206.GA2784@nuc> <m5fusq$hfd$2@ger.gmane.org>
T o n g <mlist4suntong@yahoo.com> writes:
> Ok, good to know, but that's more targeting towards package building,
> not source code developing and maintaining. Does it imply that I should
> put the `debian` folder within my source tree now? Because as mentioned
> before, the last thing I want to do is to separate my source and my
> `debian` folder into two git repos.
http://www.eyrie.org/~eagle/notes/debian/git.html#combine may (or may not)
be helpful. This is a little out of date with current tools,
unforunately. The major change is use of --upstream-vcs-tag in
git-import-orig.
Some people do find this approach too complicated. I guess I'm just used
to it, but it works for me.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: