-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> A very good start and something that could happen within hours would be
> for Karolina or a DD sponser to modify the Debian changelog for her
> packages and then upload to the normal debian archive.
With all gratitude for Karolina's work, as the formal debian maintainer for
some of these KDE modules I'd be very happy if (i) I could have some control
over what is uploaded when, i.e., upload my own packages or at least be in
personal dialogue with someone else who's uploading them, and (ii) if the
packages uploaded to debian.org used my own packaging (with help from others
of course) and not forked versions which (last time I looked) were
non-trivially different.
Read: I'd probably get a bit grumpy if some other DD uploaded a major new
upstream version to debian.org with code that differs noticeably from my own
packaging (which is available on KDE CVS) "within hours" of warning that this
were going to happen. :)
Not to be overly protective of "my" packages, but I'd like a little more
involvement in the process than Mark proposes. :)
Of course this is all moot anyway since what I upload at what time will pretty
much depend on what Chris does with kdelibs/kdebase/etc. :)
Ben.
- --
Ben Burton
[EMAIL PROTECTED] | [EMAIL PROTECTED]
Public Key: finger [EMAIL PROTECTED]
The English country gentleman galloping after a fox - the unspeakable in
full pursuit of the uneatable.
- Oscar Wilde
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9spH0MQNuxza4YcERAmSTAJ9ajb2+I366qNYbSTKONN9t86NQagCgpho6
nFc6JvI7H9ceu4pl955kUWE=
=nppU
-----END PGP SIGNATURE-----
