Re: New from emacs-snapshot
"Davide G. M. Salvetti" <firstname.lastname@example.org> writes:
> I have a branch of your archive at
> where I made some patches to allow the package to build with latest (as
> of yesterday) CVS checkouts. The problem I had with your archive is
> (primary) that the misc-unseparated.dpatch was not up-to-date, causing
> dpatch to fail. I started by disabling dpatch, just to see if things
> would have been right otherwise, then I fixed that patch and enabled it
You have two branches, -devo and -dgms. Which one should I register?
Yes. I noticed some hunk warnings. It seems you fixed
> You might want to take a look at it, and see if you would want to merge
> it back. (There is also a small fix in the rules file (use [:space:]
> instead of an explicit list of [<SPACE><TAB>], if nothing else it will
> help emacs not to mess up whenever whitespace-cleanup is used), along
> with some insignificant white space differences.)
I will surely include it.
> I'm not sure if I understood correctly how to make use of your package,
> though. This is what I do:
> - cvs checkout of emacs
> - tla get of your debian directory in emacs/debian
> - fakeroot dpkg-buildpackage
> What would be the advantages of make-dist, along with
> build-emacs-snapshot and your make-dist patch?
(FYI, I hope to see the patch applied upstream ASAP)
I'm offering you a way to give back :-)
The objective of emacs-snapshot is twofold:
1/ offering users the bleading edge Emacs since there are no upstream
releases very often
2/ preparing the next upstream release. Here I come:
make-dist is the way upstream tarballs are generated. So, generating
packages from this tarball is a better way to find out blocking problems
with a release ASAP. Then we can report them upstream instead of
discovering them very late.
You would not see those problem if you created packages directly from
the CVS checkout.