Hi, On Donnerstag, 29. Januar 2009, Johannes Sixt wrote: > The most recent entry in debian/changelog is dated 2006-09-12. This is > quite aged.
Indeed :-/
> Is there a knowledgable Debian developer who knows how to bring this file
> up-to-date in a meaningful way?
Technically, there is the nice tool dch (part of the devscripts package),
which greatly simplefies editing debian/changelog in the right format.
Contentwise the file should contain changes in the packaging. So stuff
like "new upstream version with great feature foo" or "added a depends to
libschroedinger as requiered by new upstream version" or whatever.
(So Debian packages often ship two changelog files: the upstream one and the
debian one. And I think that very much makes sense.)
> Is this file of any use for our Debian/Ubuntu packagers? Or do you keep
> your own versions of the debian/ directory anyway? What's the best way to
> proceed here?
I havent looked at cinelerra (in regards to packaging) for more then a year
probably, mostly because I'm sad that it's impossible to get cinelerra into
Debian main due to some licence problems and some embedded code copies - at
least that's what the status was last year. If this has been fixed, w00t.
That said, shipping a debian/ directory in release tarballs is usually not
helpful for maintainers as they keep there own version in some repo anyway.
If cooperation between packagers and developers exist, it's nice to have it
in the same repo but a different branch. (As to be able to make different
packaging releases based on the exact same upstream tarball/checkout.)
That said :) in future (=after Debian lenny has been released) a debian/
directory in the (upstream) tarball will be silenty thrown away anyway (by
dpkg 3.0 source format) so that the debian/ directory will always come as a
debian-diff. So I would suggest to keep it now, to not make life harder for
current users of it :)
regards,
Holger (offline written)
signature.asc
Description: This is a digitally signed message part.
