Re: KDE/Qt Status in Debian dists

1999-04-08 Thread Mike Carter
Date sent:  Wed, 07 Apr 1999 05:11:27 -0400
From:   Sean <[EMAIL PROTECTED]>
To: Terry Hancock <[EMAIL PROTECTED]>
Copies to:  debian-user@lists.debian.org
Subject:            Re: KDE/Qt Status in Debian dists

> Just bypass the whole package manager, download the source, compile and
> install. This way when you decide to upgrade you won't have to worry about
> qt-kde getting broken unless some of their support libraries change.  And
> even if that does happen, it would just mean that you would need to
> recompile & install.
> 
> Sean
> 
> 
> Terry Hancock wrote:
> 
> > Hi,
> > I've installed the "Hamm" (=2.0) distribution of Debian Linux from CD,
> > and I intended from the start to install KDE as quickly as I could, but
> > Debian has since gone to "Slink" (=2.1).
> >
> > On the Hamm CDs, the "Qt" library required by KDE is not included for
> > licensing reasons. However, the Troll Tech website claims the newer
> > versions of Qt are "free" software, apparently resolving previous
> > licensing conflicts. (?)
> >
> > The Qt library debian package _is_ on the FTP site, but unfortunately,
> > when I try to update the package from there using dselect, I get a
> > cascade of dependencies -- basically dselect wants to upgrade my whole
> > system to the Slink distribution.  This would be okay, except for the
> > downtime.
> >
> > I'd prefer to get the "Slink" CDs, but will the Qt library be on them?
> >
> > I have little time to work with this computer, and I fear that if I get
> > Slink, "Potato" will be out before I get the Qt package, and I'll be
> > back where I started. :)
> >
> > Also, can you get dselect to _downgrade_ your packages?  I've now got
> > some kind of mixture of Hamm and Slink packages on this system, and I'm
> > not sure how stable that is.  I wish dselect gave you a little more
> > control, but I haven't quite figured out how to do everything with dpkg.
> >
> > Would appreciate any help at all, thanks!
> >
> > Terry Hancock
> > [EMAIL PROTECTED]
> >

Hi team,
I downloaded the slink debs from
ftp://ftp.de.kde.org/pub/kde/stable/1.1/distribution/deb/slink/binary-i386.
I downloaded qt1g 1.42 debs from unstable. I don't recall other 
dependencies, the rest of the dependencies I think were in the kde 
debs.  So if you load in correct order kde will be up and running in no 
time.  A whole lot less than getting gnome running.  Only one set of 
dependencies external to kde  My system is hamm.
cheers, 
Mike


Re: KDE/Qt Status in Debian dists

1999-04-07 Thread Joop Stakenborg
On Wed, 07 Apr 1999, J.H.M. Dassen wrote:
> On Wed, Apr 07, 1999 at 05:11:27 -0400, Sean wrote:
> > Just bypass the whole package manager, download the source, compile and
> > install.
> 
> Bypassing the package manager is usually a bad idea, unless you compile the
> source to install outside the package manager controlled directories, e.g.
> by --prefix=/usr/local, and if necessary use "equivs" to tell the package
> management system about this software.
> 


KDE as well as Qt install into /usr/local by default.

> Ray

Greets,
Joop
--
Joop Stakenborg PA4TU
[EMAIL PROTECTED]


Re: KDE/Qt Status in Debian dists

1999-04-07 Thread Sean
J.H.M. Dassen wrote:

> On Wed, Apr 07, 1999 at 05:11:27 -0400, Sean wrote:
> > Just bypass the whole package manager, download the source, compile and
> > install.
>
> Bypassing the package manager is usually a bad idea, unless you compile the
> source to install outside the package manager controlled directories, e.g.
> by --prefix=/usr/local, and if necessary use "equivs" to tell the package
> management system about this software.

When you install compiled source it defaults to installing under /usr/local 
(99.9% of
the time).  And I don't like the idea of telling the package manager about 
stuff that
I've compiled myself, as I think that is a recipie for disaster.  What the 
package
manager doesn't know won't hurt it.

Currently I'm running Debian 2.1 with a lot of compiled software on it.  When I 
was
using 2.0, I downloaded egcs-1.1.1 and the pgcc patches, built the new
pentium-optimized compilers (I use a dual ppro system), and uninstalled the 
debian
egcs packages.  I also downloaded the qt, kde, windowmaker, gtk-1.2.1, 
gimp-1.0.4,
and gobs of other sourcecode which I have since compiled with 
pentium-optimizations
without any problems.  It all gets thrown into /usr/local/ be default so it's 
easy to
see what binaries have been produced from compilation and which ones have come 
from
packages. I then even used apt-get dist-upgrade to move from 2.0 to 2.1.  
apt-get
downloaded all the updates for the deb packages that I have installed and left 
all
the stuff I've compiled alone.  Everything still works great.

Personally this is why I like Debian.  It lets you use the package manager for 
as
much of the system as you want, but you can still compile as much or as little
software as you like to suit your particular needs.  And for some things, I much
prefer to "update" by downloading a new tarball, and running configure && make
&& make install (after slipping in the pentiumpro optimizations, of course).

Sean


Re: KDE/Qt Status in Debian dists

1999-04-07 Thread J.H.M. Dassen
On Wed, Apr 07, 1999 at 00:45:31 +, Terry Hancock wrote:
> On the Hamm CDs, the "Qt" library required by KDE is not included for
> licensing reasons.

> However, the Troll Tech website claims the newer versions of Qt are "free"
> software,

Qt 2.0 will be licensed under the QPL 1.0, which is a license that is free
according to the Debian Free Software Guidelines, and thus is suitable for
inclusion in "main".

Qt 2.0 is currently in beta; it is not released yet.

> apparently resolving previous licensing conflicts. (?)

No. The analysis given in http://www.debian.org/News/1998/19981008 still
holds for a QPL-licensed Qt, as the QPL is not a GPL-compatible license.

There have been rumours that KDE's licensing terms will change though (e.g.
by explicitly allowing KDE to be linked against a QPL-licensed Qt (a la the
LyX license (http://www.lyx.org)), or by switching to a BSD-style license),
which would resolve the licensing conflict, and allow KDE in Debian (in main
once we have Qt 2.0). I am not aware of an official promise by the KDE
developers in this regard; does someone have a pointer?

> The Qt library debian package _is_ on the FTP site, but unfortunately,
> when I try to update the package from there using dselect, I get a cascade
> of dependencies -- basically dselect wants to upgrade my whole system to
> the Slink distribution.  This would be okay, except for the downtime.

Aren't there KDE and Qt packages for Hamm in .deb format on ftp.kde.org?
(Or else, there's at least a Qt for Hamm at
http://archive.debian.org/debian-archive/dists/hamm/non-free/binary-i386/libs/).

> I'd prefer to get the "Slink" CDs, but will the Qt library be on them?

No. There was no free Qt yet at the time of Slink's code freeze; there isn't
one now yet. There is of course a Qt package for use with Slink in
dists/stable/non-free on the FTP sites.

HTH,
Ray
-- 
POPULATION EXPLOSION  Unique in human experience, an event which happened 
yesterday but which everyone swears won't happen until tomorrow.  
- The Hipcrime Vocab by Chad C. Mulligan 


Re: KDE/Qt Status in Debian dists

1999-04-07 Thread J.H.M. Dassen
On Wed, Apr 07, 1999 at 05:11:27 -0400, Sean wrote:
> Just bypass the whole package manager, download the source, compile and
> install.

Bypassing the package manager is usually a bad idea, unless you compile the
source to install outside the package manager controlled directories, e.g.
by --prefix=/usr/local, and if necessary use "equivs" to tell the package
management system about this software.

Ray
-- 
POPULATION EXPLOSION  Unique in human experience, an event which happened 
yesterday but which everyone swears won't happen until tomorrow.  
- The Hipcrime Vocab by Chad C. Mulligan 


Re: KDE/Qt Status in Debian dists

1999-04-07 Thread Sean
Just bypass the whole package manager, download the source, compile and install.
This way when you decide to upgrade you won't have to worry about qt-kde getting
broken unless some of their support libraries change.  And even if that does 
happen,
it would just mean that you would need to recompile & install.

Sean


Terry Hancock wrote:

> Hi,
> I've installed the "Hamm" (=2.0) distribution of Debian Linux from CD,
> and I intended from the
> start to install KDE as quickly as I could, but Debian has since gone to
> "Slink" (=2.1).
>
> On the Hamm CDs, the "Qt" library required by KDE is not included for
> licensing reasons.
> However, the Troll Tech website claims the newer versions of Qt are
> "free" software,
> apparently resolving previous licensing conflicts. (?)
>
> The Qt library debian package _is_ on the FTP site, but unfortunately,
> when I try to update
> the package from there using dselect, I get a cascade of dependencies --
> basically dselect
> wants to upgrade my whole system to the Slink distribution.  This would
> be okay, except for
> the downtime.
>
> I'd prefer to get the "Slink" CDs, but will the Qt library be on them?
>
> I have little time to work with this computer, and I fear that if I get
> Slink, "Potato" will be out
> before I get the Qt package, and I'll be back where I started. :)
>
> Also, can you get dselect to _downgrade_ your packages?  I've now got
> some kind of
> mixture of Hamm and Slink packages on this system, and I'm not sure how
> stable that is.  I
> wish dselect gave you a little more control, but I haven't quite figured
> out how to do everything
> with dpkg.
>
> Would appreciate any help at all, thanks!
>
> Terry Hancock
> [EMAIL PROTECTED]
>
> --
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null