k3b CVS HEAD

Just so's y'all know, I'm working on integrating Brueffer's k3b patches from 
the ports into KDE CVS (perhaps with a little d-pointer magic to reduce the 
number of #ifdef FreeBSDs in the header files). (Concrete reason for doing 
this: Mignon wants to burn a CD of baby pix, and I don't feel like explaining 
mkisofs). 

--

-- 
   "On top of that [watching KDE CVS] is interesting in a perverse 
    way, like watching sausage get made. By very smart people." - dkite

Re: k3b CVS HEAD

By chance, is this a patch to make k3b work with burncd, or does it still only 
work with SCSI?

On Thursday 01 July 2004 05:48 am, Adriaan de Groot wrote:
> Just so's y'all know, I'm working on integrating Brueffer's k3b patches
> from the ports into KDE CVS (perhaps with a little d-pointer magic to
> reduce the number of #ifdef FreeBSDs in the header files). (Concrete reason
> for doing this: Mignon wants to burn a CD of baby pix, and I don't feel
> like explaining mkisofs).

Re: k3b CVS HEAD

On Thursday 01 July 2004 12:48, Adriaan de Groot wrote:
> Just so's y'all know, I'm working on integrating Brueffer's k3b patches
> from the ports into KDE CVS (perhaps with a little d-pointer magic to
> reduce the number of #ifdef FreeBSDs in the header files). (Concrete reason
> for doing this: Mignon wants to burn a CD of baby pix, and I don't feel
> like explaining mkisofs).

This is great news, but to clear some things up and hopefully reduce some 
confusion:

brueffer <at> FreeBSD.org = brueffer in #kde-freebsd who mainly does doc-related 
things (and who doesn't even use KDE)

markus <at> FreeBSD.org = me = markus (formerly buff) in #kde-freebsd who does 
everything concerning KDE on FreeBSD (in respect of us two)

Furthermode it wasn't me who ported K3B to FreeBSD. It was Heiner Eichmann who 
initially wrote the patches and still keeps them up-to-date (great job 
Heiner!). I was only a testslave who helped him in times where he didn't have 
a DVD-Burner and a 5.x-box. and who frequently bugged the people in 
#kde-freebsd to commit his PRs :).

Adriaan: I think it would be best to talk to Heiner directly, since AFAIK he 
already asked the authors to integrate his patches into KDE CVS, but for some 
reason they only did it in a very limited way.

Best regards,

Markus

Re: k3b CVS HEAD

On Thursday 01 July 2004 14:07, Justin wrote:
> By chance, is this a patch to make k3b work with burncd, or does it still
> only work with SCSI?

No, he is talking about the patchset that makes K3B work on FreeBSD with 
SCSI-burners (or ATAPICAM) and which lives in ${PORTSDIR}/sysutils/k3b/files.

Markus

--

-- 
Markus Brueffer    | GPG-Key: http://people.FreeBSD.org/~markus/markus.asc
markus <at> brueffer.de | FP: 3F9B EBE8 F290 E5CC 1447 8760 D48D 1072 78F8 A8D4
markus <at> FreeBSD.org | FreeBSD: The Power to Serve!

_______________________________________________
kde-freebsd mailing list
kde-freebsd <at> freebsd.kde.org
http://freebsd.kde.org/mailman/listinfo/kde-freebsd

Re: k3b CVS HEAD

On Thursday 01 July 2004 14:07, Justin wrote:
> By chance, is this a patch to make k3b work with burncd, or does it still
> only work with SCSI?

Didn't I do that, like tupping ages ago? Or perhaps that was for a different 
app, like kreatecd. KDE apps that call external cdrecord can generally be 
ported to burncd, although if they're too tied to stupid ways of discovering 
the devices in the system it can be tedious.

--

-- 
   "On top of that [watching KDE CVS] is interesting in a perverse 
    way, like watching sausage get made. By very smart people." - dkite

Re: k3b CVS HEAD

On Thursday 01 July 2004 14:25, Markus Brueffer wrote:
> On Thursday 01 July 2004 12:48, Adriaan de Groot wrote:
> > Just so's y'all know, I'm working on integrating Brueffer's k3b patches
> > from the ports into KDE CVS (perhaps with a little d-pointer magic to
> > reduce the number of #ifdef FreeBSDs in the header files). (Concrete
> > reason for doing this: Mignon wants to burn a CD of baby pix, and I don't
> > feel like explaining mkisofs).

Ok, ok, _some_ Brueffer's patches. I still can't keep y'all apart, sorry. 
Which of the two was at LinuxTag?

> Furthermode it wasn't me who ported K3B to FreeBSD. It was Heiner Eichmann
> who initially wrote the patches and still keeps them up-to-date (great job
> Heiner!). I was only a testslave who helped him in times where he didn't
> have a DVD-Burner and a 5.x-box. and who frequently bugged the people in
> #kde-freebsd to commit his PRs :).

OK, I'll talk to Heiner. Since I can just commit stuff to KDE CVS, we can push 
it in like that. There's only minor changes needed for most of the patches, I 
think.

--

-- 
   "On top of that [watching KDE CVS] is interesting in a perverse 
    way, like watching sausage get made. By very smart people." - dkite

Freelance outsourcing

Hi
Just a note to introduce our unique service. We have over 300 of the top professionals available to complete
your project should you wish to outsource. 
Designers, Programmers, Translators, Writers to name but a few. We can guarantee you a top quality service
for a lot less money. 

You only make payment upon 100% satisfaction. 

If you should require any outsourced projects to be completed, then please give us a try you’ll be
surprised. Our freelancers will price your project and offer you their services. You will have our
satisfaction backup guarantee.

Logo’s, Web design, Back end programmimg, Copy writing, Translation etc.

Regards
John Thompson
admin <at> eurofreelancers.com

www.eurofreelancers.com

Re: k3b CVS HEAD

Hi1

Some statements from my side.

- The current BSD port is a bit outdated (0.11.9 vs. 0.11.12). The reason is 
my limited time. The latest version already exists but requires testing. I 
can submit it as it is and let the users test. I do not expect problems, as 
0.11.10 - 0.11.12 are just bug fix releases....

- I still do not have a dvd burner, so volunteer testers a always welcome.

- The patches are not in the k3b source code because I did not give them to 
the author. I gave him minor things, which he submitted, but not the big 
parts. There are two reasons for that: first, if the author changes stuff in 
the #ifdef linux part, I will not notice. The FreeBSd part will just not 
work. Keeping the patch separate will hopefull cause a ptach error, which is 
a hint for me to look for the cause. Second: I am not a cam expert (and I did 
not find one so far). So the patches are changeing as, bug reports come in. 
Having them separate makes the fixing of BSD specific issues easier. I would 
like to leave it that way, at least for some time.

- At least one patch (the drive detection) makes the original code imho 
unmaintainable. The reason is a different philosophie: k3b iterates through a 
set of device names, calling an ioctl to find out, if it is a cd or dvd 
drive. I call a cam function to get a list of cam devices and use them. 
Making the k3b source code compatible to this approach requires some work of 
the original author. I would NOT ask him to merge my patch into his code!

- I did not understand the original question: Adriaan, what are you planning 
exactly? Merging the patches to the original k3b source code? Storing the 

Re: k3b CVS HEAD

On Thursday 01 July 2004 19:44, Heiner wrote:
> - The current BSD port is a bit outdated (0.11.9 vs. 0.11.12). The reason
> is my limited time. The latest version already exists but requires testing.
> I can submit it as it is and let the users test. I do not expect problems,
> as 0.11.10 - 0.11.12 are just bug fix releases....

At least the src-device patches applied without any problem at all.

> - The patches are not in the k3b source code because I did not give them to
> the author. I gave him minor things, which he submitted, but not the big
> parts. There are two reasons for that: first, if the author changes stuff
> in the #ifdef linux part, I will not notice. The FreeBSd part will just not
> work. Keeping the patch separate will hopefull cause a ptach error, which
> is a hint for me to look for the cause. Second: I am not a cam expert (and
> I did not find one so far). So the patches are changeing as, bug reports
> come in. Having them separate makes the fixing of BSD specific issues
> easier. I would like to leave it that way, at least for some time.

OK. I like to have everything in the upstream, since after all we pretend to 
be a cross-platform desktop environment. I'll leave it alone for now then, at 
least as far as committing to KDE CVS goes.

--

-- 
   "On top of that [watching KDE CVS] is interesting in a perverse 
    way, like watching sausage get made. By very smart people." - dkite

Re: kde cvs on 5.2.1

The promised followup: in short, no dice.  I removed all xorg packages,
compiled Xfree86 4.3.0 from ports (the full meta-package), recompiled
qt33, arts, kdelibs, and kdebase, and it is still dying with the same
backtrace   This is getting slightly discouraging, as I don't have
the fastest computer ever and a complete recompile takes a while (I
started immediately after my last email, and finished just a couple
minutes ago).  Any ideas of where to go now?  Backtrace and ldd of
konsole following:

Program received signal SIGSEGV, Segmentation fault.
0x28c308ac in qt_set_x11_resources(char const*, char const*, char
const*, char const*) () from /usr/X11R6/lib/libqt-mt.so.3
(gdb) bt
#0  0x28c308ac in qt_set_x11_resources(char const*, char const*, char
const*, char const*) ()
   from /usr/X11R6/lib/libqt-mt.so.3
#1  0x28c349f3 in qt_init_internal(int*, char**, _XDisplay*, unsigned
long, unsigned long) ()
   from /usr/X11R6/lib/libqt-mt.so.3
#2  0x28c3598d in qt_init(_XDisplay*, unsigned long, unsigned long) ()
from /usr/X11R6/lib/libqt-mt.so.3
#3  0x28c9edc9 in QApplication::QApplication(_XDisplay*, int, char**,
unsigned long, unsigned long) ()
   from /usr/X11R6/lib/libqt-mt.so.3
#4  0x28879e58 in KApplication::KApplication(_XDisplay*, unsigned long,
unsigned long, bool) ()
   from /usr/local/kde/lib/libkdecore.so.6
#5  0x280a7129 in kdemain () from
/usr/local/kde/lib/libkdeinit_konsole.so