Where are the debian KDE3 sources?
I'm considering building KDE3, and just got a bunch of it from CVS at kde.org. I did this partly because the unofficial debs were debs only, no sources that I saw (at http://www.geniussystems.net/KDE3%20Experimental/). So I have a couple of questions. Where are the current debian sources for KDE3? Would trying to apply the diff's from Debian (official or not) to the head of the kde.org tree be a good idea or not? Is there any particular harm in just following the KDE instructions for building a trial installation, without worrying about the debian stuff? By the way, I'm also interested in how these issues might play out for other packages, but since I'm focussing on KDE now I thought I'd ask here. If you can cc me on the response I'd appreciate it, since I'm only reading the list via the web archives. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where are the debian KDE3 sources?
On Friday 03 May 2002 6:56 am, Ross Boylan wrote: > Would trying to apply the diff's from Debian (official or not) to the > head of the kde.org tree be a good idea or not? The debian/ build directory is already in upstream. I've no idea what the other patches are for... > Is there any particular harm in just following the KDE instructions > for building a trial installation, without worrying about the debian stuff? Not really, that's what I do. -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://chrishowells.co.uk, PGP key: http://chrishowells.co.uk/pgp.txt KDE: http://www.koffice.org, http://edu.kde.org, http://usability.kde.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 lock screen, 'incorrect password' (my ****)
On Thu, 2 May 2002, Stephan Jaensch wrote: > You didn't compile PAM support in. Make sure you have libpam0g-dev installed > and reconfigure kdebase. Make sure that it found PAM support, make, make > install and be happy. :-) ah... that might be it :-) (although hitting the 'administrator mode' in kcontrol doesn't have the same problem). I'll see how i get on... -- Giles Constant, Systems Programmer Hyperlink Interactive http://www.hyperlink-interactive.co.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[no subject]
가브리엘향수 파운데이션 총알청바지 \25,000 \39,000 \31,500 허락 없이 메일을 보내드려 죄송합니다. 원치 않으시면 옆의 버튼을 눌러주세요. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 lock screen, 'incorrect password' (my ****)
That worked.. ta :-) On Fri, 3 May 2002, I wrote: > On Thu, 2 May 2002, Stephan Jaensch wrote: > > > You didn't compile PAM support in. Make sure you have libpam0g-dev installed > > and reconfigure kdebase. Make sure that it found PAM support, make, make > > install and be happy. :-) > > ah... that might be it :-) (although hitting the 'administrator > mode' in kcontrol doesn't have the same problem). > > I'll see how i get on... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 lock screen, 'incorrect password' (my ****)
On Fri, May 03, 2002 at 10:06:37AM +0100, Giles Constant wrote: > On Thu, 2 May 2002, Stephan Jaensch wrote: > > > You didn't compile PAM support in. > > ah... that might be it :-) > alternatively you could just make sure kcheckpass has read access to /etc/shadow, that is, make it setuid root or setgid shadow. > (although hitting the 'administrator mode' in kcontrol doesn't have > the same problem). > kdesu is just a wrapper around the system's su, so it has no permission problem. greetings -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- The problem with making software idiot-proof is that idiots are so clever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where are the debian KDE3 sources?
On Fri, May 03, 2002 at 09:01:58AM +0100, Chris Howells wrote: > On Friday 03 May 2002 6:56 am, Ross Boylan wrote: > > > Would trying to apply the diff's from Debian (official or not) to the > > head of the kde.org tree be a good idea or not? > > The debian/ build directory is already in upstream. I've no idea what the > other patches are for... My understanding from earlier discussion on this list is that although the upstream has a debian directory, it is not necessarily current. The maintainer for some of the packages said he was using upstream, but his packages do not include the core KDE ones. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where are the debian KDE3 sources?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 03 May 2002 6:30 pm, Ross Boylan wrote: > My understanding from earlier discussion on this list is that although > the upstream has a debian directory, it is not necessarily current. > The maintainer for some of the packages said he was using upstream, > but his packages do not include the core KDE ones. Hrm, I thought that all of the Debian KDE packagers had KDE CVS accounts and did the work there. Anyway, you can use webcvs to check the activity: e.g. http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/debian/ - -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://chrishowells.co.uk, PGP key: http://chrishowells.co.uk/pgp.txt KDE: http://www.koffice.org, http://edu.kde.org, http://usability.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE80s9vF8Iu1zN5WiwRAjEWAKCWmeHXzANu/0xLKqoe5S0/LdKP+wCeN84P LXzR8ZAs+SZQfOC5f83Iqk4= =dowK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Which QT?
Hi all, I've been toying with the 'best' method of compiling KDE3 on woody lately, and in the interests of lazyness I'm wondering whether it's a good idea to use woodys qt3 packages. Everything (almost) has compiled fine using those, seems very stable. If I were to have compiled qt3 myself though, could I expect any noticable leaps in performance? Any qt specific optimizations I could/should use? There was one niggle taking this shortcut, kdegraphics won't compile. It requires imlib, imlib requires an older version libpng whose -dev package conflicts with the libpng-dev package that qt3 wants, in short imlib and qt3 dev files won't coexist, I can't compile kdegraphics. Should I just forget about this and start over with a custom built qt3 perhaps like I should have done the first time around? -- dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where are the debian KDE3 sources?
fredagen den 3 maj 2002 19.30 skrev Ross Boylan: > My understanding from earlier discussion on this list is that although > the upstream has a debian directory, it is not necessarily current. > The maintainer for some of the packages said he was using upstream, > but his packages do not include the core KDE ones. True, true. I have tried it. Most packages compile with a little tweaking. Just don't count on getting it through a compile without knowing how to tweak debian files to build or knowing what to do when a KDE build fails. -- Karolina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which QT?
fredagen den 3 maj 2002 20.22 skrev Dan Slatford: > There was one niggle taking this shortcut, kdegraphics won't compile. It > requires imlib, imlib requires an older version libpng whose -dev package > conflicts with the libpng-dev package that qt3 wants, in short imlib and > qt3 dev files won't coexist, I can't compile kdegraphics. Should I just > forget about this and start over with a custom built qt3 perhaps like I > should have done the first time around? I tried by taking the imlib, changing in the deb files and recompiling. It cleanly recompiles and kdegraphics builds. But I did not do any extensive testing of the result. -- Karolina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which QT?
> I've been toying with the 'best' method of compiling KDE3 on woody lately, > and in the interests of lazyness I'm wondering whether it's a good idea to > use woodys qt3 packages. It's quite easy to compile on woody. > Everything (almost) has compiled fine using those, seems very stable. If I > were to have compiled qt3 myself though, could I expect any noticable leaps > in performance? Any qt specific optimizations I could/should use? I don't know. > There was one niggle taking this shortcut, kdegraphics won't compile. It > requires imlib, imlib requires an older version libpng whose -dev package > conflicts with the libpng-dev package that qt3 wants, in short imlib and qt3 > dev files won't coexist, I can't compile kdegraphics. Should I just forget > about this and start over with a custom built qt3 perhaps like I should have > done the first time around? Yes. Fred -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where are the debian KDE3 sources?
On Fri, May 03, 2002 at 09:47:37PM +0200, Karolina Lindqvist wrote: > fredagen den 3 maj 2002 19.30 skrev Ross Boylan: > > > My understanding from earlier discussion on this list is that although > > the upstream has a debian directory, it is not necessarily current. > > The maintainer for some of the packages said he was using upstream, > > but his packages do not include the core KDE ones. > > True, true. I have tried it. Most packages compile with a little tweaking. > Just don't count on getting it through a compile without knowing how to tweak > debian files to build or knowing what to do when a KDE build fails. My packages should compile out of KDE 3.0 BRANCH as is unless something has changed in the past week. Afaik all my changes are checked into cvs as well, although I have not ported them to HEAD (3.1) yet. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
