have not tried KDE 2.0 or haven't done so in awhile (i.e. since July or
before), you should try this. This version is extremely stable and offers
better functionality than before. This update also introduces the KDE2
modules kdegraphics and kdemultimedia to our ports tree. Additionally,
this marks the first time FreeBSD packages were announced as part of the
KDE2 beta release announcement! :-)
Most (if not all) of the remaining modules in KDE2 will be added for the
update WRT the final release.
A hack was added to fix building with SSL in kdelibs; this has been merged
in the main tree and will go away with 2.0 release update. Thanks to David
Faure <david@mandrakesoft.com> for his help regarding this.
Also, building the docs should now succeed because I've added a build
dependency on jade and linuxdoc (should be enough).
People can get my precompiled packages from the usual location on the KDE
FTP server (should spread to the mirrors Real Soon Now (tm)):
http://ftp.kde.org/pub/kde/unstable/distribution/2.0Beta5/tar/FreeBSD/
Have fun! Remember to reports bugs through http://bugs.kde.org/.
dependencies to kde2, and add koffice to kde2, because it's part of the
2.0 release. Fix my bogon in forgetting to remove obsolete qt22 patches.
The current state of the ports as far as building and installing is quite
good, but I expect minor problems with PLISTs other than for the ones I've
fixed here. I'm going to let bento figure it out. :-)
Please, test these ports and report bugs to submit@bugs.kde.org, and send
me problems with the ports themselves. I've found that KDE2 seems to have
stabilized significantly since the last snapshot.
And now, I am removing the last patch remaining in the KDE2 ports, except
for the QT 2.2 snapshot.
I can address some of its issues (should see it marked un-broken in about
3 hours, if they're trivial enough). It took too long to get this update
out the door... :-(
This is a rather stable version of KDE2. Release is hoped for sometime
next month, so I'm going to try to reroll snapshots this weekend.
Also decide policy by removing the interactive requirement in qt22's
configure script. I don't know why they bothered adding it there..
Bugged by: *many* bug-reports, requests, etc.
After short discussion with Imura-san, back out GIF-by-default until I can
confirm whether or not there are license issues with Unisys. I will deal
with this later. I should note that I'd committed to qt2[12] previously
without conferring with him on the GIF issue first.
One big ouchie: I didn't even set MASTER_SITE/MASTER_SITE_SUBDIR on qt22
properly.. but oh well. Nobody's perfect. :-)
Things should be un-broken now.. please test these ports! I'll be trying
to update them to a new snap after a week or so.
Pointy hat: will
Patches graciously submitted by: nra
Konqueror can load HTML documents, KOffice works semi-well, and KDE2 in
general seems less buggy. Only kdeutils was left out of this mega-update.
However, it should return soon. :-)
The massive reduction in patches is mostly the result of using perl
regex replacement. This reduces the amount of time it will take in the
future to upgrade these ports, and load on the repository.
QT 2.2.0beta0 (aka qt-copy) is officially enabled for the express
purpose of allowing KDE2 to compile. It is available in the qt22 port.
Additionally, GIF support is re-enabled in both Qt2 ports, so that
people can now read GIF images. GIF support is enabled through an
internal GIF reader in Qt, and requires no patented libraries. Special
effort was made to ensure that people do not install both qt21 and qt22
ports at the same time.
I'd like to take a moment to thank the following people for their help:
Alex Zepeda <jazepeda@pacbell.net>, Stephan Kulow <coolo@kde.org>, Harri
Porten <porten@kde.org>, Waldo Bastian <waba@kde.org>, Marc G. Fournier
<scrappy@hub.org>, Arun Sharma <adsharma@sharmas.dhs.org>, Matthias
Hoelzer-Kluepfel <mhk@caldera.de>, and many others. Over 150 hours of hard
work, testing, etc. were put into this update. Another couple hundred of
hours were spent by CPUs trying to compile this behemoth. :->
Special thanks to: Physics Computer Network @ Purdue staff, especially
C. Stephen Gunn <csg@physics.purdue.edu>, for giving
me access to an extremely fast machine for doing
test builds (it performed 12 full builds of the
entire suite in the last 7 days).
PR: 18838
Submitted by: Arun Sharma <adsharma@sharmas.dhs.org>
Approved by: imura, asami
previous commit message to bsd.port.mk, which said INSTALL_SHLIBS. Boo.)
Line up the rhs of variable assignments nicely. Remove a couple of extra
whitespaces while I'm here.
Suggested by: sobomax
problems by disabling ODBC library building. Apparently kdenetwork2
doesn't need that support (it does need mimelib), so we're all right
on that!
This is the import of KDESUPPORT and KDENETWORK 1.90 (aka KDE2 beta).
Repo-copies by: asami
Only changed giflib -> libungif in kdegraphics.
They realy do NOT want libgif, and do NOT use libgif anywhere.
Some ports are checking its existence in configure, but they
are nonsense at all!!
bsd.port.mk rev. 1.304 for details on the change.
The fix here is one of the following.
(1) Define USE_BZIP2 instead of BUILD_DEPENDS on bzip2 and redefining
EXTRACT_* commands.
(2) Change ${EXTRACT_CMD} to ${TAR} when the command is obviously
calling the "tar" command (i.e., arguments like "-xzf" are spelled
out).
(3) If ${EXTRACT_CMD} is called directly with ${EXTRACT_BEFORE_ARGS},
add ${EXTRACT_AFTER_ARGS} to the command line as well.
(4) If any of EXTRACT_CMD, EXTRACT_BEFORE_ARGS or EXTRACT_AFTER_ARGS
is set, define the other two too.
This port requireat least s version 1.41 of the Qt library.
There will be an error reported by configure, if only an earlier
version is found, but no automatic port dependency exists (i.e.
the x11-toolkits/qt141 port has to be manually built and installed).
There may still be a problem with a missing -lXext in the kdesupport
port. This will be taken care of during the next few days, if the
problem still exists ...
installs the version of the port that uses shared library number 9 and the
LIBRARY_VERSION set to the default. Normally this is against our policy
(bumping the version number for minor things), however due to the major
problems caused with the upgrade, Satoshi and I decided that this was best.
Approved by: asami
