[kde-freebsd] [SVN Commit] area51/PORTS/graphics/kphotoalbum-kde4
SVN commit 8946 by avilla: - Fix plist. M +237 -0pkg-plist ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] [PATCH] CLucene 0.9.x - 2.3.x
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-16 01:42:15 -0500, Baptiste Daroussin wrote: On Tue, Jan 15, 2013 at 07:20:37PM -0500, Jung-uk Kim wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-15 10:05:01 -0500, Max Brazhnikov wrote: On Fri, 11 Jan 2013 17:41:02 -0500, Jung-uk Kim wrote: LibreOffice 3.6 and later requires CLucene 2.3 but we have 0.9.x in the source tree. I'd like to import it now before we start working on LO. Please see attached clucene2.diff. Changes: - Upgrade CLucene 0.9.21 to the last stable version, i. e., 0.9.21b. - Import CLucene 2.3.3.4. It is required by LibreOffice 3.6 and later. - Register conflicts between 0.9.x and 2.3.x. Please review the attached patch. I see no reason to keep old clucene, it's unmaintained upstream. I'd deprecated textproc/p5-Lucene and updated textproc/clucene directly to 2.x. Although I agree with you in general, we can't just set it BROKEN without the maintainers' consent, can we? (FYI, textproc/p5-Lucene is maintained by perl@). First yes we can, if there is really no other choice, secondly given that nothing depends on it, I approve the BROKEN. Okay. If clsung and tj agree, then we can upgrade clucene and remove clucene-contrib. Who's going to be the maintainer, then? regards, Bapt with perl@ hat :) Ah, I forgot that you have many many hats in your closet. ;-) JK -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJQ9viKAAoJECXpabHZMqHOwEEH/i8Tuu1J3pvNxrBONtVYVfW+ CrzZNZDuYhCXlGiX4AjBHQV5iswA1VfmwBTgq+OvJMSWTkgbKUziCL2CdQRfTKrH gFJwtgbidzMr+eMyN5uTl+w6wKWcfIgDUC57Y93/CNQ8MZS96BdYSpXF2FDkcw4G a40PSOaK3q7Xkn0u8TDAhswf07sbQsJEeBEQYvPAXq/u3XU5nzLSp0t/4lnPtli5 akUMB6B0sWbVpMNffzZ2sY1+Nh2JVwENA7iFlfPG4sGwVAzC1WNDAeYBDZeifRsh TsUuh05LpUGkulPMERaK/C/KZu5dVbjKDvpxtHrwyOjEPeaRae4wVQ0n4MgjbSc= =k2G6 -END PGP SIGNATURE- ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] [PATCH] CLucene 0.9.x - 2.3.x
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/16/13 1:59 PM, Jung-uk Kim wrote: On 2013-01-16 01:42:15 -0500, Baptiste Daroussin wrote: On Tue, Jan 15, 2013 at 07:20:37PM -0500, Jung-uk Kim wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-15 10:05:01 -0500, Max Brazhnikov wrote: On Fri, 11 Jan 2013 17:41:02 -0500, Jung-uk Kim wrote: LibreOffice 3.6 and later requires CLucene 2.3 but we have 0.9.x in the source tree. I'd like to import it now before we start working on LO. Please see attached clucene2.diff. Changes: - Upgrade CLucene 0.9.21 to the last stable version, i. e., 0.9.21b. - Import CLucene 2.3.3.4. It is required by LibreOffice 3.6 and later. - Register conflicts between 0.9.x and 2.3.x. Please review the attached patch. I see no reason to keep old clucene, it's unmaintained upstream. I'd deprecated textproc/p5-Lucene and updated textproc/clucene directly to 2.x. Although I agree with you in general, we can't just set it BROKEN without the maintainers' consent, can we? (FYI, textproc/p5-Lucene is maintained by perl@). First yes we can, if there is really no other choice, secondly given that nothing depends on it, I approve the BROKEN. Okay. If clsung and tj agree, then we can upgrade clucene and remove clucene-contrib. Who's going to be the maintainer, then? This is fine by me. Tom - -- FreeBSD Ports Committer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ9wHCAAoJEEJSM9yB4iIWopwH/jand+vhZdwIykIxESukIvBD Su8wmD0sHR5qa6I+Dbqgo3itJWRZuoK2QGwzNWJw4jcMN5kElVV310Hiy4wC3i3h pv6ObypaIiNFcz/u1QAkTI1iO16P8pXz/rghfmFQuSMb9mp9o0nWn8e3Z9FIyKmq InUDlWHD/+pEbjBqgdNmpg+CjveRI9yO4BBnmdv6tABgZRfmTgYWQUzcFe9fMotR 9WXJ/mx7MHo8sAkI5QfqjyCr1WRJ6Kc6lHaOGKVm+fqENhV4Z4+hH07HglAoy0Y4 Js9pkUQUSZZXfUHF2QbpLGksle7YVYyzH02zgjVDFbWQ929TP2KEodKv5IjJLJc= =gS+h -END PGP SIGNATURE- ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] FreeBSD 8.2 with pre-built KDE 3.5 package from FreeBSD 7.1 DVD
Hi everybody, I know that I am not subscribed to this list, but getting on here seems to be a somewhat difficult task and I promise that my email won't be a spam one :) My issue is the following: As far as I know, FreeBSD has completely dropped support for KDE 3.5. Whether it's the ports, or the pkg_add precompiled binaries. Am I right in assuming this? I am currently running a live version of FreeBSD 8.2 with KDE 4.8. The thing here is that KDE 4 is simply too heavy for my system. For example: it is impossible for me to have two open shells at the same time. Once I exit a given shell, I can't open another one due to a lack of resources, even after having turned off all the extra stuff - plasma desktop, nepomuk... As a consequence, I can see myself do two possible things, to have a system running with KDE 3.5 once again: 1. go back to an older release of FreeBSD and install KDE 3.5 from the precompiled binaries that are on the DVD donwload version. Judging by the release announcements, this should be 7.1. http://www.freebsd.org/releases/7.1R/announce.html This is something that I don't really feel like doing. 2. To be honest, I am quite happy with 8.2 and I would like to keep it for some time to come. In other words, is there a way to keep 8.2 and still have KDE 3.5 along with it? For example has anyone ever tried to install a 7.1 pre-built package (KDE 3.5 in this case) on an 8.2 system? Is that possible? Any other solutions? Many thanks Georg___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] FreeBSD 8.2 with pre-built KDE 3.5 package from FreeBSD 7.1 DVD
On 2013-01-18 01:21:11 Georg Reilinger wrote: Hi everybody, I know that I am not subscribed to this list, but getting on here seems to be a somewhat difficult task and I promise that my email won't be a spam one :) Getting on the list is quite easy, just send an email to kde-freebsd-requ...@kde.org with title subscribe. IIRC you will then be sent a confirmation email that requests you to visit an URL. My issue is the following: As far as I know, FreeBSD has completely dropped support for KDE 3.5. Whether it's the ports, or the pkg_add precompiled binaries. Am I right in assuming this? There were discussions on this multiple times on the freebsd-ports mailing list in the last two years and I haven't followed them all but AFAIK it's unsupported now after having been marked deprecated/broken/ignore for ages. pkg_* is basically ports without the need to compile things yourself. I am currently running a live version of FreeBSD 8.2 with KDE 4.8. The thing here is that KDE 4 is simply too heavy for my system. For example: it is impossible for me to have two open shells at the same time. Once I exit a given shell, I can't open another one due to a lack of resources, even after having turned off all the extra stuff - plasma desktop, nepomuk... The two konsole instances will share almost all of their memory though, and if you restart a konsole the new one should claim about the same amount of memory than it's precedor did, therefore the cause of this is very likely somewhere else (I suspect dbus is to be blamed). When you can't open a new konsole the next time, can you try opening a xterm and launching konsole from that xterm? The xterm might report some information about konsole's doings that way. Some analysis... Did you check the sysctl recommendation in x11-toolkits/qt4-gui/pkg-message in the ports collection? Have you verified you are runing out of resources (i.e. out of memory or oom kernel messages) or are you just suspecting it? What proccesses are the largest memory consumers when OOM happens, and what is the kill order of the OOM recovery? Is it only konsole that can't be started or are other kde applications affected, too? If not, can non-kde memory hogs (openoffice, evolution, firefox, java*, ...) be started? If not, can any graphical applications at all be started (by a KDE interface)? How much phyiscal and swap memory is avaliable to the system? As a consequence, I can see myself do two possible things, to have a system running with KDE 3.5 once again: 1. go back to an older release of FreeBSD and install KDE 3.5 from the precompiled binaries that are on the DVD donwload version. Judging by the release announcements, this should be 7.1. http://www.freebsd.org/releases/7.1R/announce.html This is something that I don't really feel like doing. 2. To be honest, I am quite happy with 8.2 and I would like to keep it for some time to come. In other words, is there a way to keep 8.2 and still have KDE 3.5 along with it? For example has anyone ever tried to install a 7.1 pre-built package (KDE 3.5 in this case) on an 8.2 system? Is that possible? Any other solutions? (1) FreeBSD (in theory) has backward compatibily back to the 1990s. Therefore you can use elements of FreeBSD-7.1 in a 8.2 installation. If the userspace lacks files or symbols inside libraries, is otherwise incompatible, or you just want to go the safe way to begin with, you can install 7.1 into /compat or some other path of your choice and chroot into it. Afterwards install the desired packages into the chrooted 7.1 installation and the host system should be able run them. There's a wiki entry for running wine in a 32-bit FreeBSD-8 chroot inside a 64-bit FreeBSD-8 system, in your case it would be a FreeBSD-7 chroot inside a FreeBSD-8 system, the procedure to do this is more or less the same (during that guide, /usr/src would need to contain FreeBSD-7.1, /usr/ports be the old ports, and so on). https://wiki.freebsd.org/Wine You will need the COMPAT_FREEBSD7 kernel option (which is enabled by default on all official releases and GENERIC). (2) Given the fact KDE-3 is no longer maintained by the KDE-SC project, the fact KDE-3 was just as bloated and therefore (for those days) resource hungry as KDE-4 is now, as well as the fact it lacks many modern desktop features nevertheless, you might want to take a look at xfce4. While it lacks many features of KDE-4 it's a solid desktop environment, actively developed and supported and also has a much lower memory footprint than KDE or GNOME. freshports: http://www.freshports.org/x11-wm/xfce4 At this point however I will tell you my Atom D330 can run KDE-4.8 on FreeBSD-9 with 512MB physical memory + 4GB swap and it's quite usable. I.e. it's still usable with multiple konsole windows open at the same time, and I didn't even bother to disable nepomuk, akonadi and their DBMS friends. (3) OpenBSD and NetBSD
