On Tuesday 06 September 2005 12:21, Kevin wrote: > On 9/6/05, Dave Feustel <[EMAIL PROTECTED]> wrote: > > How does one resume a previously stopped make in > > /usr/ports/x11/kde? The normal method of simply > > re-invoking make restarted the entire make from the > > beginning. > > Unfortunately, if it's starting an entire built, this is probably what > you actually need to do, as if the necessary packages had actually > built, a 'make install' will immediately return to command line inside > a given port.. > > If you're curious to see what packages are built you can: > > ls /usr/ports/packages/<arch>/all/
In this directory is nothing but cups-1.1.23p2.tgz > Also, if you want to go through the process manually, here's what a > make install for any port actually does: > > make fetch > make extract > make patch > make configure > make build > make package > make install The automatic CVS-based process works amazingly well. There just seem to be a few problems with building the KDE packages, the causes of which I haven't figured out yet. > I'm curious though, unless you have some specific reason to use ports, > why not skip the pain / hassle / time, and just use the pre-built > packages? It is this process above from which they originate. The pre-built OpenBSD KDE packages are generally 6-9 months out of date. (I'm running KDE 3.3.2 on OpenBSD 3.7. The current version of KDE is 3.4.2, KDE 3.5 is on the way and KDE 4 is being discussed on the KDE mailing lists. QT 4.0.1 is out, although it can't be used with any KDE but version 4, AFAIK) It's hard to get support from the KDE mailing lists for problems with that software since I am not running the most recent release. Since I spend almost all of my time using KDE software, my goal is to build and install the latest KDE/Qt releases as soon as they become available. As of today I am ready to start using KDE's websvn to build a kde.org version of KDE software releases to use instead of the OpenBSD version. > Generally, unless I have a compelling reason to use a port (i.e. a > missing package on a non i386 platform is usually the reason), I use > the package instead. I've been using the OpenBSD KDE/Qt packages for about 3-4 years. Now I want to build it myself to have more current versions. Dave -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
