On Thu, 11 Sep 2003 18:27:34 +0200 (MEST) Svetoslav Slavtchev <[EMAIL PROTECTED]> wrote:
> > On Thu, 11 Sep 2003 09:29:11 +0200 (MEST) > > Svetoslav Slavtchev <[EMAIL PROTECTED]> wrote: > > > > > an update for dvd+rw-tools is needed for support of data dvd copy > > > (and making k3b quiet ) > > > > > > i tried to package current cvs > > > (anyone interested to review the spec ? , and may be upload to contrib) > > > > > > http://varna.demon.co.uk/~svetlio/ruby-contrib/mdk-cook/hack-k3b/ > > > > I can upload k3b into contrib, but I don't have write access in main, > > maybe > > CC'ing the maintainer or filing a bugreport in bugzilla against > > dvd+rw-tools > > is a good idea? > > :) > 1.) bug report, that the version is not current? > (pretty much packages could fall in this criteria :) ) Ah, it's also a version update... I didn't really look at that, but you will want to mail warly that you want to upgrade it from 5.11.4.6.4 to 5.12.4.7.4, and why. He only wants version upgrades in main with a good reason, and since he is also the maintainer of the package, you need him. > or it causes a worning with not included package because of 1.) Ehh, just a warning, and everything works ok for the rest? Maybe the warning can be disabled in k3b_0.10 in some way? No idea yet. > > For hack-k3b, I'd rather name it k3b_0.10 or k3b_0.10cvs or so, because > > it's > > just a cvs release, not a hacked up release, right? > > should i change it, or it's not a problem for you ? Sorry, I wasn't clear. It was decided a while ago that packages which are patched by mandrake, can be called hack%name, because it's a hacked up version of the original. I think there was a cdrecord package which deserved that name. Most packages which are called hack%name are not much more then development releases from the projects cvs (hackabiword, hackeroaster), so the preferred name would then be something like k3b_0.10, or k3b_0.10cvs, like the gettext_0.12 package in contrib. Just compare it to sylpheed and sylpheed-claws, both codebases for essentially the same project. I don't really care of it should be k3b_0.10 or k3b_0.10cvs, but there are libpackages made from it also, and a libk3b_0.100 as packagename is rather confusing, while libk3b_0.10cvs0 sounds just a bit more sane :-) I can change it, that's not too much trouble. I was asking to check if hack-k3b was the right naming or not, and what your opinion is about it. -- Marcel Pol
