[Pkg-kde-talk] KDE 3.4 package underway

[Christopher Martin]

--nextPart1180436.Y1P5iZCBe6
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On March 2, 2005 16:14, Adeodato Sim=F3 wrote:
>   They were created. It seems that they don't do it for betas.

Ah, OK. In future, do you prefer to create orig.tar.gz with the build files=
=20
included, or (my preference) without, the buildprep.diff containing=20
everything?

> > I think it's nice to have all the build-system stuff in a nice,
> > separate patch. It can then be removed easily (just unpatch),
> > re-applied, etc. It's more a matter of "style" and of how you like to
> > work than an important technical decision, though as a group we should
> > probably try to be consistent. Comments from anyone and everyone?
>
>   As I said, I agree that the little effort is worth it. Also, note that
>   when doing this, "unpack the orig.tar.gz and put the debian/ from SVN
>   on it" just works out the box (i.e., no chance of not shipping
>   autotools changes because one used the svn dir but forgot to run make
>   -f admin/Makefile.common dist).

True. I had envisioned the buildprep.diff as being created by the uploader=
=20
every time, but now that you mention it, I suppose we could simply create=20
the buildprep.diff after each upstream release/branch pull/new patch that=20
affects the build system, and check it into svn. Then everything is=20
absolutely standardized, and it's really easy to start a build.

Cheers,
Christopher

--nextPart1180436.Y1P5iZCBe6
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Signed by Christopher Martin <chrsmrtn@freeshell.org>

iD8DBQBCJjSWU+gWW+vtsysRAoO6AJ0U+6Mp/qqsG7iDd1QmTQ+v7zS6SgCglF3U
l44mlomzlHDYuJ5AUIi0tCU=
=ISQt
-----END PGP SIGNATURE-----

--nextPart1180436.Y1P5iZCBe6--