[Pkg-running-devel] forerunner 310xt support for garmin-ant-downlaoder

[Kristof Ralovich]

On Thu, Oct 10, 2013 at 8:24 PM, Ralf Treinen <treinen at free.fr> wrote:

> Hello,
>
> > Thank you again for the guidance.
> >
> > I can report some success, I've figured out a sequence of operations
> that allow
> > me to push patches into the "upstream" branch, and in the end generate
> the new
> > .deb package from the "master" branch. Assuming that the new upstream
> version
> > will be 1.0, here is the recipe:
> >
> >
> > # git clone ...
> > git checkout upstream
> >
> > # 1. work,
> > # 2. commit,
> > # 3. goto 1.
> > # ...
> > # done
>
> Why are you working on the upstream branch? Aren't you going to release
> your software independently from debian?
>
> In that case you would create your release whereever that is (ususally
> not debian). Once you have your 1.0.orig.tar.gz tarball, you import it
> with git-import-orig.
>
> -Ralf.
>
> I started working on the upstream branch, as g-a-d doesn't have a real
upstream project any more. This is what I was trying to ask in my original
email. What is the preferred way of development (providing patches)? I
assumed the implicit answer of working on the upstream branch.

My software is already released independently from debian, see
https://code.google.com/p/antpm . The second reason I started working on
the upstream branch was that I would like to merge antpm in there, that is
fuse antpm into g-a-d.

The third reason I started working on the upstream branch was to e.g. close
bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690068, for that I
basically needed to figure out a way to commit fixes in the upstream
branch, so i could still test-build a working .deb package from master
afterwards.

If you would like me to, I can host the new "upstream repository" on github
or somewhere else (and it will be based on the current upstream branch in
debian, as that is the latest code). Please let me know if i should do that!

Thanks,
Kristof
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-running-devel/attachments/20131010/c92f4448/attachment.html>