The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
|
Over 40 comments listed.
Printing out index only. |
One thing to watch out for...
by Benjamin Reed on Sunday 23/Sep/2001, @00:34
|
Although the symlink is fixed now for /usr/share/config/kdm, if you've changed your kdm settings at all from what was in the default RPMs (like changed the background color or logo or whatever), the directory will be renamed kdm.rpmsave and the symlink will replace it, but will not contain your "saved" files, so kdm *still* won't start.
I don't have the time to do this build tonight, it's already 3:30am for me, but I'll see if I can fix the rpms (or check for fixed ones in rawhide) and get them put together. Other than that, I'm running the 7.1 rpms on my desktop and it's looking pretty smooth.
|
[
Reply To This | View ]
|
|
|
Vivat packages for RH6.x
by Milan Svoboda on Sunday 23/Sep/2001, @02:47
|
It's perfect. I haven't reinstall my linux box :-)
|
[
Reply To This | View ]
|
Distributed KDE Packaging to acclerated KDE develo
by Asif Ali Rizwaan on Sunday 23/Sep/2001, @06:50
|
I would like to discuss a very simple way to improve and accelerate kde and
koffice development by breaking big packages to smaller ones. So, the objectives are:
1. Ease KDE package download and Installation.
2. Respecting Users' need and Avoiding unwanted package installation
3. Freeing up the clogged ftp servers :)
4. Easy upgrade of specific packages using KDE-Installer or manually
5. Easy Access to sources and More bug fixes by users and new kde developers.
6. Overall satisfied KDE user
To-do: break every big source package to about 1-2 MB maximum size (depending on the sources) but not more than 3 MB. The Kdebase, Kdelibs, Kdegames and other packages are of huge sizes :( kdebase=10MB, kdelibs=5+MB, Kdegames=10+MB and so on. I would suggest that these huge packages be broken into smaller bits, like:
------------------------
kdebase.core.tar.bz2
kdebase.konqueror.tar.bz2
kdebase.kicker.tar.bz2
kdebase.kcontrol.tar.bz2
kdebase.kate.tar.bz2
kdebase.kpersonalizer.tar.bz2
kdebase.ktip.tar.bz2
------------------------
likewise kdegames can be parted into many smaller packages:
------------------------
kdegames.kpat.tar.bz2
kdegames.sokoban.tar.bz2
kdegames.kwin4.tar.bz2
kdegames.kmines.tar.bz2
------------------------
I'm not asking to change the default way of distributing the sources and binary packages but asking for one more folder in the ftp.kde.org and its mirror which contains a folder 'separated' or 'Distributed' or whatever you may like, which will contain the split-upped kde packages.
1. Ease Download and (binary) Installation: no big deal, rpm, tar.bz2 and tar.gz or debs, will be quite smaller so it will reduce the download time required, you would appreciate this if you have a modem dial-up connection.
2. Avoiding unwanted packages: a typical kde user may not like to have all the package kde provides, take me for example, I really love to have the following games in kdegames package:
a. Patience
b. Kmines
c. Sirtet
d. Jezzball
and I do not want to have other games of the default kdegames package. I have no other option to discard those games from my installation (but to install and delete). if kdegames has a distributed smaller packages like:
i. kdegames.kpat.tar.bz2
ii. kdegames.kmines.tar.bz2
iii. kdegames.sirtet.tar.bz2
iv. kdegames.kjezz.tar.bz2
in this way I can get what I really need. And due to this huge size of kdegames new games cannot be included into the package like knights a nice chess frontend (http://knights.sourceforge.net) which is around 1MB of size. It could be easily become a package of kdegames as:
kdegames.knights.tar.bz2
In the Koffice I would love to have (download and install) only two Kword and Kspread, as like many kde users don't have to use other koffice apps even rarely. It would be nice to see:
i. koffice.kword.tar.bz2
ii. koffice.kspread.tar.bz2
iii. koffice.kpresenter.tar.bz2
iv. koffice.krayon.tar.bz2 (etc.)
3. Freeing up clogged ftp servers: As the packages become smaller (around 1-3 MB), the download time reduces considerably and hence ftp servers become unclogged and will be accessible for more people.
4. Easy Upgrade of Specific KDE apps using KDE-Installer or manually: most kde users just wish for individual konqueror, kmail, and other apps updates, but they could not do so at present. As I am happy for KDE 3.0's inclusion of kde-installer, but I am afraid it will also try to download the huge kde packages again making itself rather useless, except installing packages in proper sequence. The Kde-Installer will be benefitted with this type of distributed kde packages, allowing more flexibility and options to choose from. KDE-Installer can allow individual package upgrades like konqueror (satisfying the dependencies) or other apps. Users can also download their preferred apps for upgrading.
5. Easy Access to Source and More Bug Fixes: kde users and new kde developers are discouraged by the huge source sizes to download 10MB kdebase source to just to tweak a bit here or there. I was discouraged and unhappily forced to download 10MB kdebase.tar.bz2, just to check out and modify the kicker sources or to get (31k) cursor_large.bdf sources from kcontrol/input :( with which I created the white mouse cursor for KDE/X.
Not just tweaks, the bugs can be located and fixed easily as it get easy to check out the sources by new and experienced kde developers alike with the new 'distributed kde packages'.
6. Overall Satisfied KDE users: these things will definitely satisfy a kde user:
a. Reduced time on downloading source/binary kde packages
b. Easy, fast Accessible ftp download
c. Individual package upgrade
d. Easy to access source code
e. Fully (almost) customized kde
f. Easy installation with kde-installer
g. Alpha, Beta, RC1 etc version can be accessible to user (due to small package sizes)
I know that there are other factors affecting the above points like bandwidth, knowhow etc., I believe that the 'Distributed KDE Packages' will accelerate and improve kde development. And I would appreciate if the KDE Team kindly allow these distributed packages along with the standard (or current) packages. Thanks for reading up to this point ;)
|
[
Reply To This | View ]
|
|
|
redcarpet is great
by bondowine on Sunday 23/Sep/2001, @10:58
|
RedCarpet!!!!!!!
|
[
Reply To This | View ]
|
|
|
Order of installing RH 7.1 RPMS for KDE 2.2.1
by Jeff on Sunday 23/Sep/2001, @13:29
|
Ok, maybe this qualifies as a "stupid question," but I bet a few other people are wondering as well...
Is there a certain order to install the RH 7.1 RPMS that will help all the dependency problems? If I just try to do *.rpm for all the packages, I get a hoard of dependency issues (with a stock RH 7.1 install). If I installed them in a certain order would it help this, as it seems like certain new packages depend of certain other new packages...
I don't want to do a --force and risk really screwing up my system.
Thanks,
Jeff
|
[
Reply To This | View ]
|
|
|
Thanks !!!!!!!
by Eduardo Sanchez on Sunday 23/Sep/2001, @14:46
|
Thank you Benjamin ! This is what I was looking for !
Thank you very much!
|
[
Reply To This | View ]
|
Where do you start?
by Me on Sunday 23/Sep/2001, @16:05
|
I hope I don't sound stupid, but where do you start? I see a directory full of rpm's, but none that obviously says that it is the first to download, or which other ones to download to get things started.
-- IV
|
[
Reply To This | View ]
|
|
|
FreeBSD packages any soon?
by J Blazevic on Sunday 23/Sep/2001, @16:10
|
I hope that somebody will release FreeBSD packages, I tried texstar's objprelink RPMs and although the release is just 0.0.1 it is really a vast improvement over 2.2 especially in stability department. Konqi is so bloody good!
|
[
Reply To This | View ]
|
Is it running on AMD K6-2 ?
by Krame on Sunday 23/Sep/2001, @16:11
|
I wasn't able to run previous KDE2.2 packages on my AMD K6-2 ( i585 ), so I'would like to ask if someone with K6 checked those new packages. I'm trying to avoid downloading all packages ( with my low-bandwidth connection ... ) only to see that they are not working.
|
[
Reply To This | View ]
|
|
|
FTP a tad overloaded... =)
by Benjamin Reed on Sunday 23/Sep/2001, @17:13
|
The FTP server is going a bit wiggy, but it looks like the RPMs have made it to kde.org's FTP site at ftp://ftp.kde.org/pub/kde/stable/2.2.1/RedHat-unofficial/, so feel free to grab them there instead. ;)
|
[
Reply To This | View ]
|
Erg... CUPS
by Rob Knop on Sunday 23/Sep/2001, @20:11
|
OK, I'm sure that CUPS is much better than LPRng. On the other hand, I had LPRng configured and working with my two printers (old Canon BJ200ex on parallel, Epson 860 on USB).
Does kdelibs really require cups? The RPM is claiming that it needs CUPS in order to be installed, and CUPS won't let itself be installed unless I remove LPRng.
So I remove LPRng and install CUPS. However, as best I can tell, your CUPS RPM here doesn't support USB printers. Is this correct?
I'm one who uses Gnome most of the time... I'd love to try out KE 2.2.1, but ideally I'd like to do it with a minimum of pain. If I can get my printers working easily with CUPS, then great, otherwise, I'll wait for something which integrates better with RedHat 7.1.
-Rob
|
[
Reply To This | View ]
|
|
|
Who IS Benjamin Reed?
by Albert Schueller on Sunday 23/Sep/2001, @22:31
|
Installing rpms built by people you don't know is one of the biggest security threats for linux users. You should only install rpms from trusted sources, e.g. ftp.kde.org. If Mr. Reed really wants to package KDE, he should convince the maintainers of ftp.kde.org to post them. There is safety in numbers, lots of people using the rpms means lots of people to figure out if they are trojan horses. I have very little doubt that Mr. Reed is an honest volunteer of his time, but this issue should be at the forefront of anyone's mind as s/he downloads and installs rpms. I also have very little doubt that there are rpms out there, even in trusted locations, that have trojans inside them.
|
[
Reply To This | View ]
|
|
|
Objprelinked ?
by Biswapesh on Sunday 23/Sep/2001, @22:44
|
Hi Ben
Thanks for the RPMs - I spent hours doing rpm --rebuild on Bero's SRPMS, unfortunately, too many dependencies and takes too much time.
Question: Are the RPMs objprelinked ? Apparantly, it makes a big difference to startup speeds (I have objprelink installed though I guess that wouldn't make much difference).
- Biswa.
|
[
Reply To This | View ]
|
RH7.1 dependancy?
by Anonymous Coward on Sunday 23/Sep/2001, @23:07
|
I have tried the rpms, and am stalled at installing kdelibs. I have resolved all buy libxstl and libxml2, of which I don't seem to find RPMs from RedHat. Would anyone know where I can find the appropriate RPMs for the above two dependancies? Thanks in advance
|
[
Reply To This | View ]
|
|
|
Dependency problems
by Wendell on Monday 24/Sep/2001, @06:13
|
This is what I get when I try to install the libs.
I don't see an rpm for kdesupport. Do I need that?
Thanks.
Found 0 source and 1 binary packages
Dependency Problem:
kdelibs is needed by kdelibs-devel-2.2.1-0.rh71.1.cups
pcre-devel is needed by kdelibs-devel-2.2.1-0.rh71.1.cups
kdesupport-devel is needed by kdevelop-1.4.1-2
kdesupport-devel is needed by kdevelop-1.4.1-2
kdelibs-devel is needed by kdelibs-sound-devel-2.1.1-5
kdelibs-devel is needed by kdelibs-sound-devel-2.1.1-5
|
[
Reply To This | View ]
|
|
|
vorbis, lower versions?
by Mary on Tuesday 25/Sep/2001, @18:52
|
When I loaded the rpms for kde2.2.1 for rh7.1, I came up with the following questions:
1) kdebase says that it requires vorbis, but doesn't specify the version. The only one that I can find via rpmfind is libvorbis-1.0rc2-2.i386.rpm from rawhide, which does not seem to satisfy the dependency, as rpm -V kdebase.... still complains. This package does not seem to be included with the non-kde packages on the download site.
2) the following packages seem to have LOWER versions than the ones that I previously loaded for kde 2.2. The previous versions are in parens and I got them by following the links on the kde website:
kdemultimedia-2.2-0.rh7x.1.i386.rpm (2.2-3)
kdemultimedia-devel-2.2-0.rh7x.1.i386.rpm (2.2-3)
kdepim-2.2-0.rh7x.1.i386.rpm (2.2-1)
kdepim-devel-2.2-0.rh7x.1.i386.rpm (2.2-1)
kdeutils-2.2-0.rh7x.1.i386.rpm (2.2-2)
kdoc-2.2-0.rh7x.1.noarch.rpm (2.2-1)
|
[
Reply To This | View ]
|
Cannot change fonts
by binand on Wednesday 26/Sep/2001, @04:31
|
Hi Ben,
With these RPMs, I cannot change the fonts in KDE. Everytime I change the fonts in Control Center->Look and Feel->Fonts, the new settings are reset to the defaults upon restart. And the defaults are pretty bad (on my system, at least).
Anything I missed?
|
[
Reply To This | View ]
|
|
|
LAME dependencies
by Jim on Wednesday 26/Sep/2001, @12:00
|
Hi all,
I'm trying to install kdebase, but I get dependencies for lame >=2.89 and libmp3lame.so.0. I've looked for a suitable lame rpm on the net -- no luck. I have just finished downloading and compiling the lame source (works OK), but that doesn't solve my RPM dependency issue. Is lame included in one of the other packages that need to be installed prior to kdebase? I HAVE installed the (4) kdelibs -- but that also does not help. Any ideas? Thanx.
|
[
Reply To This | View ]
|
|
|
can't send email with kmail 2.2.1
by Joe VanAndel on Thursday 27/Sep/2001, @10:24
|
I've tried both the 'sendmail' and 'SMTP' options. Netscape uses SMTP, and it works fine. 'Mail' uses 'sendmail' (local to my machine), which also works
When I send mail, I get the message (on the bottom line of Kmail)
Unrecognized transport protocol, could not send message
|
[
Reply To This | View ]
|
|
|
Thank you Ben!
by Rokko on Saturday 29/Sep/2001, @05:29
|
U R A god.
|
[
Reply To This | View ]
|
Thank you Ben!
by Rokko on Saturday 29/Sep/2001, @05:29
|
U R A god.
|
[
Reply To This | View ]
|
how about solaris pkgs
by Mark on Monday 01/Oct/2001, @12:34
|
2.1.1 is on ftp.patriotsoft.com but they haven't released any since.
|
[
Reply To This | View ]
|
Thank you Benjamin Reed!
by Greg Hildstrom on Tuesday 02/Oct/2001, @08:31
|
Hello. I currently develop beowulf software for the Naval Surface Warfare Center in Bethesda, MD. I had been using KDevelop 1.3 for development, but I wanted to upgrade to the latest one, which requires and is bundled with KDE 2.2.1. Using his "unofficial" Red Hat 7.1 packages, it took me about 1.5 hours to upgrade. It took me a while to locate and take care of certain dependencies, but persistence pays off.
KDE 2.2.1 is a beautiful and functional interface. KDevelop 2.0.1 seems an order of magnitude better than the version 1.4 packaged with Red Hat 7.1 (no more 'unknown child process died' messages').
I would recommend the upgrade. Thanks for all of the help in response to other users questions. That helped me out a lot.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
Posted by Dre on Saturday 22/Sep/2001, @20:46