[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: First bits of collab infrastructure ready to go


Am Freitag, den 03.07.2009, 18:04 -0500 schrieb John Goerzen:
> > If you didn’t know it, you can keep debian/changelog entries and git
> > commit messages in sync by using:
> > $ # do your changes
> > $ dch "Your message"
> > $ debcommit -a
> You can also go the other way by committing changesets in git, and using
> git-dch to propogate them to debian/changelog.

I tried that a few times, and found the results sometime not very
appealing. Especially that you need to run git-dch exactly once per
upload, IIRC.

Is there a disadvantage of using dch&debcommit?

> > I think it’s ok to go by git-buildpackage’s defaults, at least in the
> > cases where we do not import an upstream repository. If we do, we need
> > to check whether we want to separate between upstream and upstream-dist
> > (i.e. the contents of upstream’s VCS and of upstream’s released
> > tarballs).
> That's probably OK overall, but inconvenient if upstream is also part of
> the team, speaking selfishly.

Good point. I leave it to you in this case :-).

Also, "Setup.hs sdist" does not change or add files, does it? This
probably helps, compared to the rather severe changes that an automake
dist tarball contains.


PS: John, are you at DebConf? We could do some more
getting-pkg-haskell-going there. I know that Marco unfortunately can’t
come, and haven’t heard of others.
Joachim "nomeata" Breitner
Debian Developer
  nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Reply to: