Re: KDE3 apps replacements?
Quoting Thomas Mueller : from Per olof Ljungmark: I am finally in the process of removing KDE3 completely, switched to Xfce some time ago, and wonder if any of you could recommend suitable replacements for some of the apps: kpdfpdf viewer with the ability to copy text from kWrite simple text editor with some filetype and highlighting features + easy to switch encoding (vim/gvim?) kPatience Card game, Freecell in particular kColorChooser pick html color names kRuler Pixel screen ruler kSnapshot Screen dump to jpg and/or png I use xpdf, found it much better than kpdf but that was some years ago when I used KDE in Slackware Linux. I see there are other open-source pdf viewers. System Rescue CD uses epdfview. I didn't like kWrite or kspread (spreadsheet that came with KDE). Abiword is much better than kWrite, and gnumeric is much better than the spreadsheet that came with KDE. I am not familiar with the other KDE apps. Tom Hi, I just tried graphics/electrix which seems good enough. For spreadsheet and serious word processing I already use OpenOffice, kwrite was ideal for quick and simple editing. Found Pysol for patience, will test it. //pet -- Intersonic AB Registered in Solna, Sweden SE556539368201 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 apps replacements?
Quoting Thomas Mueller : from Per olof Ljungmark: I am finally in the process of removing KDE3 completely, switched to Xfce some time ago, and wonder if any of you could recommend suitable replacements for some of the apps: kpdfpdf viewer with the ability to copy text from kWrite simple text editor with some filetype and highlighting features + easy to switch encoding (vim/gvim?) kPatience Card game, Freecell in particular kColorChooser pick html color names kRuler Pixel screen ruler kSnapshot Screen dump to jpg and/or png I use xpdf, found it much better than kpdf but that was some years ago when I used KDE in Slackware Linux. I see there are other open-source pdf viewers. System Rescue CD uses epdfview. I didn't like kWrite or kspread (spreadsheet that came with KDE). Abiword is much better than kWrite, and gnumeric is much better than the spreadsheet that came with KDE. I am not familiar with the other KDE apps. Tom Hi, I just tried graphics/electrix which seems good enough. For spreadsheet and serious word processing I already use OpenOffice, kwrite was ideal for quick and simple editing. Found Pysol for patience, will test it. //pet -- Intersonic AB Registered in Solna, Sweden SE556539368201 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 apps replacements?
from Per olof Ljungmark: > I am finally in the process of removing KDE3 completely, switched to > Xfce some time ago, and wonder if any of you could recommend suitable > replacements for some of the apps: > kpdfpdf viewer with the ability to copy text from > kWrite simple text editor with some filetype and highlighting > features + easy to switch encoding (vim/gvim?) > kPatience Card game, Freecell in particular > kColorChooser pick html color names > kRuler Pixel screen ruler > kSnapshot Screen dump to jpg and/or png I use xpdf, found it much better than kpdf but that was some years ago when I used KDE in Slackware Linux. I see there are other open-source pdf viewers. System Rescue CD uses epdfview. I didn't like kWrite or kspread (spreadsheet that came with KDE). Abiword is much better than kWrite, and gnumeric is much better than the spreadsheet that came with KDE. I am not familiar with the other KDE apps. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 apps replacements?
2013/10/13 Per olof Ljungmark : > Hi, > > I am finally in the process of removing KDE3 completely, switched to > Xfce some time ago, and wonder if any of you could recommend suitable > replacements for some of the apps: > > kpdfpdf viewer with the ability to copy text from In Gtk, you can try: - graphics/epdfview - graphics/electrix - graphics/evince (needs GNOME dependencies) or graphics/mupdf > kWrite simple text editor with some filetype and highlighting Xfce provides editors/mousepad, since 0.3.0 release, it uses gtksourceview (syntax highlighting), but there're editors/geany, editors/emacs... > features + easy to switch encoding (vim/gvim?) > kPatience Card game, Freecell in particular > kColorChooser pick html color names > kRuler Pixel screen ruler No games with Xfce, you should see KDE4 and / or GNOME. > kSnapshot Screen dump to jpg and/or png x11/xfce4-screenshooter-plugin (it's an application) is equivalent to ksnapshot. > > Thank you! > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- olivier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
KDE3 apps replacements?
Hi, I am finally in the process of removing KDE3 completely, switched to Xfce some time ago, and wonder if any of you could recommend suitable replacements for some of the apps: kpdfpdf viewer with the ability to copy text from kWrite simple text editor with some filetype and highlighting features + easy to switch encoding (vim/gvim?) kPatience Card game, Freecell in particular kColorChooser pick html color names kRuler Pixel screen ruler kSnapshot Screen dump to jpg and/or png Thank you! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 / QT3 update (more removals)
Am 05.07.2013 00:27 (UTC+1) schrieb René Ladan: > Hi, > > after closer inspection I discovered there are some 100 more ports that > are affected by the KDE3 / QT3 removal, I generated a new patch at [1]. > You might want to look at the update to MOVED to see if your port is > there, patches for non-core QT3/KDE3 ports are welcome. > > There are also a few ports [2] that could trivially be modified to live > without KDE3 / QT3, those are already updated or PRs have been sent to > their maintainers (these ports are also included in [1]). > > I intend to send [1] for an exp-run after the ports at [2] have been > updated (or maintainer timed out). > > [1] ftp://rene-ladan.nl/pub/freebsd/kde3-rm.diff > SIZE = 9403670 > SHA256 = 1a1bafd9e0425fa2599aff34772e0bbb44aa6865e10d290198d362740f3facc3 > > ftp://rene-ladan.nl/pub/freebsd/kde3-rm-ndd.diff (same patch but with > svn --no-diff-deleted) > SIZE = 361117 > SHA256 = abf23ececa1c067797c550a517c2605d46dfeb6d773348fc30a0964a7fc8b999 > > [2] port PR maintainer > astro/celestia 180265 danfe@ Hi René, many thanks for your work. But I think there are some ports we should prove carefully before deleting them unnecessarily. For example for astro/celestia it should be sufficient to remove the kde3 UI, shouldn't it? As another example it should be ok to only remove the qt3 option of sysutils/nvclock to keep the port alive. Or do I miss something here? Regards, Rainer > comms/unixcw 180280 db@ > emulators/pearpc 180277 novel@ > emulators/tiemu3 180279 cyberb...@cyberbotx.com > games/nethack33 180273 glewis@ > games/nethack34 180275 glewis@ > graphics/gnash 180271 dinoex@ > multimedia/dvbcut 180272 se@ > net/avahi-app 180266 gnome@ > net-p2p 180212 sil...@ultrasoft.ee > security/pinentry 180278 makc@ > sysutils/nvclock 180276 danfe@ > > René ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
KDE3 / QT3 update (more removals)
Hi, after closer inspection I discovered there are some 100 more ports that are affected by the KDE3 / QT3 removal, I generated a new patch at [1]. You might want to look at the update to MOVED to see if your port is there, patches for non-core QT3/KDE3 ports are welcome. There are also a few ports [2] that could trivially be modified to live without KDE3 / QT3, those are already updated or PRs have been sent to their maintainers (these ports are also included in [1]). I intend to send [1] for an exp-run after the ports at [2] have been updated (or maintainer timed out). [1] ftp://rene-ladan.nl/pub/freebsd/kde3-rm.diff SIZE = 9403670 SHA256 = 1a1bafd9e0425fa2599aff34772e0bbb44aa6865e10d290198d362740f3facc3 ftp://rene-ladan.nl/pub/freebsd/kde3-rm-ndd.diff (same patch but with svn --no-diff-deleted) SIZE = 361117 SHA256 = abf23ececa1c067797c550a517c2605d46dfeb6d773348fc30a0964a7fc8b999 [2] port PR maintainer astro/celestia 180265 danfe@ comms/unixcw 180280 db@ emulators/pearpc 180277 novel@ emulators/tiemu3 180279 cyberb...@cyberbotx.com games/nethack33 180273 glewis@ games/nethack34 180275 glewis@ graphics/gnash 180271 dinoex@ multimedia/dvbcut 180272 se@ net/avahi-app 180266 gnome@ net-p2p 180212 sil...@ultrasoft.ee security/pinentry 180278 makc@ sysutils/nvclock 180276 danfe@ René ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On Tue, Jul 2, 2013 at 9:34 PM, Per olof Ljungmark wrote: > On 2013-07-02 18:31, Daniel Nebdal wrote: >> On Tue, Jul 2, 2013 at 5:55 PM, Jim Pingle wrote: >>> On 07/02/13 07:10, Matthias Apitz wrote: >>>> El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet >>>> escribió: >>>> >>>>> bsdstats.org > ports stats would have that information probably >>>> >>>> http://bsdstats.org/ports.php?category=91 >>>> >>>> says in column 'times in use': >>>> >>>> x11/kde3: 534 >>>> x11/kde4: 86 >>> >>> I feel as though I'm in the happy minority who use and enjoy KDE4. My >>> FreeBSD desktop/workstation is running it well but it does not have >>> limited resource requirements (i7-750, 8G of RAM, Radeon HD 4650). >>> >>> Since Amarok and K3B outgrew their KDE3 dependencies, I've managed to >>> keep my system KDE3/QT3-free for a while now, though that wasn't always >>> easy in the past. >>> >>> The only real hiccup I've had was the recent KDE4 bump that made me have >>> to reconfigure some things, but it ended up working better than ever in >>> the end. The only current complaint I have is about the atrocities they >>> have committed to KMail. >>> >>> Resource usage and philosophical reasons aside, some people who have >>> been burned by KDE4 in the past may want to revisit it now, it's matured >>> a lot from its early days. >>> >>> Personally I won't miss KDE3 at all, and I really haven't missed it for >>> several years now. >>> >>> Jim >> >> >> I was about to write something similar. My work machine has been on >> KDE4 for years, and though it was quite rocky in the earlier versions >> it has kind of quietly disappeared into the background (in a good way) >> now - while I can understand the gnome2 revival projects, I don't >> quite see the point of e.g. Trinity. > > Of course KDE4 works and many people use it daily - but for me who got > used to a fairly stripped desktop with just the basics I work with all > the time KDE4 was just in the way, in fact, it made me work more on > Windows XP. > > My hope now is that xfce grows just a little bit more in functionality > to be roughly a KDE3 successor. > > //per I haven't tried it, but Razor-Qt looks like a reasonable environment as well - though you need to add apps, like, oh, the KDE4 ones. Which might not be quite what you were after. x) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
patch to remove KDE3/QT3
Hi, (CC'd maintainers of ports that are scheduled for removal) I have prepared a patch to remove the KDE3 and QT3 ports, it is available at [1]. This patch also: - removes ports/Mk/bsd.kde.mk (only used for KDE3/QT3) - patches bsd.port.mk (removes USE_KDEBASE_VER, USE_KDELIBS_VER, USE_QT_VER) - undocuments the KDE and QT knobs (ports should use the KDE4 and QT4 knobs instead) - updates CHANGES Two more ports, graphics/kipi-plugins net-p2p/museekplus, use QT3 but are not part of KDE3 and can easily be modified to live without. I have PRs for those to their maintainers. A local INDEX-9 build is fine, not sure if we want an exp-run for this? [1] ftp://rene-ladan.nl/pub/freebsd/kde3-rm.diff % ls -l kde3-rm.diff -rw-r--r-- 1 rene ftp 7811874 Jul 2 22:10 kde3-rm.diff % sha256 kde3-rm.diff SHA256 (kde3-rm.diff) = 91d7dc21a7121fc8121d73959067d795e0941d5f4a1d64de0c06915adc4febe3 % Regards, René ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On 2013-07-02 18:31, Daniel Nebdal wrote: > On Tue, Jul 2, 2013 at 5:55 PM, Jim Pingle wrote: >> On 07/02/13 07:10, Matthias Apitz wrote: >>> El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet >>> escribió: >>> >>>> bsdstats.org > ports stats would have that information probably >>> >>> http://bsdstats.org/ports.php?category=91 >>> >>> says in column 'times in use': >>> >>> x11/kde3: 534 >>> x11/kde4: 86 >> >> I feel as though I'm in the happy minority who use and enjoy KDE4. My >> FreeBSD desktop/workstation is running it well but it does not have >> limited resource requirements (i7-750, 8G of RAM, Radeon HD 4650). >> >> Since Amarok and K3B outgrew their KDE3 dependencies, I've managed to >> keep my system KDE3/QT3-free for a while now, though that wasn't always >> easy in the past. >> >> The only real hiccup I've had was the recent KDE4 bump that made me have >> to reconfigure some things, but it ended up working better than ever in >> the end. The only current complaint I have is about the atrocities they >> have committed to KMail. >> >> Resource usage and philosophical reasons aside, some people who have >> been burned by KDE4 in the past may want to revisit it now, it's matured >> a lot from its early days. >> >> Personally I won't miss KDE3 at all, and I really haven't missed it for >> several years now. >> >> Jim > > > I was about to write something similar. My work machine has been on > KDE4 for years, and though it was quite rocky in the earlier versions > it has kind of quietly disappeared into the background (in a good way) > now - while I can understand the gnome2 revival projects, I don't > quite see the point of e.g. Trinity. Of course KDE4 works and many people use it daily - but for me who got used to a fairly stripped desktop with just the basics I work with all the time KDE4 was just in the way, in fact, it made me work more on Windows XP. My hope now is that xfce grows just a little bit more in functionality to be roughly a KDE3 successor. //per ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On Tue, Jul 2, 2013 at 5:55 PM, Jim Pingle wrote: > On 07/02/13 07:10, Matthias Apitz wrote: >> El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet >> escribió: >> >>> bsdstats.org > ports stats would have that information probably >> >> http://bsdstats.org/ports.php?category=91 >> >> says in column 'times in use': >> >> x11/kde3: 534 >> x11/kde4: 86 > > I feel as though I'm in the happy minority who use and enjoy KDE4. My > FreeBSD desktop/workstation is running it well but it does not have > limited resource requirements (i7-750, 8G of RAM, Radeon HD 4650). > > Since Amarok and K3B outgrew their KDE3 dependencies, I've managed to > keep my system KDE3/QT3-free for a while now, though that wasn't always > easy in the past. > > The only real hiccup I've had was the recent KDE4 bump that made me have > to reconfigure some things, but it ended up working better than ever in > the end. The only current complaint I have is about the atrocities they > have committed to KMail. > > Resource usage and philosophical reasons aside, some people who have > been burned by KDE4 in the past may want to revisit it now, it's matured > a lot from its early days. > > Personally I won't miss KDE3 at all, and I really haven't missed it for > several years now. > > Jim I was about to write something similar. My work machine has been on KDE4 for years, and though it was quite rocky in the earlier versions it has kind of quietly disappeared into the background (in a good way) now - while I can understand the gnome2 revival projects, I don't quite see the point of e.g. Trinity. -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On 07/02/13 07:10, Matthias Apitz wrote: > El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet > escribió: > >> bsdstats.org > ports stats would have that information probably > > http://bsdstats.org/ports.php?category=91 > > says in column 'times in use': > > x11/kde3: 534 > x11/kde4: 86 I feel as though I'm in the happy minority who use and enjoy KDE4. My FreeBSD desktop/workstation is running it well but it does not have limited resource requirements (i7-750, 8G of RAM, Radeon HD 4650). Since Amarok and K3B outgrew their KDE3 dependencies, I've managed to keep my system KDE3/QT3-free for a while now, though that wasn't always easy in the past. The only real hiccup I've had was the recent KDE4 bump that made me have to reconfigure some things, but it ended up working better than ever in the end. The only current complaint I have is about the atrocities they have committed to KMail. Resource usage and philosophical reasons aside, some people who have been burned by KDE4 in the past may want to revisit it now, it's matured a lot from its early days. Personally I won't miss KDE3 at all, and I really haven't missed it for several years now. Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On 07/02/13 07:10, Matthias Apitz wrote: El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet escribió: bsdstats.org > ports stats would have that information probably http://bsdstats.org/ports.php?category=91 says in column 'times in use': x11/kde3: 534 x11/kde4: 86 matthias We should add those who uninstalled KDE3, knowing it would soon be removed, but are still missing it. I, for one, moved to XFCE "before it's too late", but feel I've lost a lot. Just my 2c. bye av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
René Ladan wrote: > On 02-07-2013 07:10, Matthias Apitz wrote: > > El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey > > Bouquet escribió: > > > >> bsdstats.org > ports stats would have that information probably > > > > http://bsdstats.org/ports.php?category=91 (bsdstats.org contact cc'ed) bsdstats.org seems to be broken. I get the following error when trying to access http://bsdstats.org/freebsd/ Warning: require_once(BSDSmarty.class.php): failed to open stream: No such file or directory in /usr/local/www/bsdstats.org/www/freebsd/index.php on line 3 Fatal error: require_once(): Failed opening required 'BSDSmarty.class.php' (include_path='.:/usr/local/share/pear') in /usr/local/www/bsdstats.org/www/freebsd/index.php on line 3 Emanuel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On 02-07-2013 07:10, Matthias Apitz wrote: > El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet escribió: > >> bsdstats.org > ports stats would have that information probably > > http://bsdstats.org/ports.php?category=91 > > says in column 'times in use': > > x11/kde3: 534 > x11/kde4: 86 > So? 1. Collecting statistics is voluntary, so it could be that more people have installed kde4 than kde3 but not the reporting tool (sysutils/bsdstats). 2. There are multiple ports which do not exist anymore but are still listed there, e.g. x11-wm/xfce with 649 users or x11/qt1 (15 users). So either these ports are still in use (!) or the data is outdated. 3. FreeBSD releases look up-to-date, but are most people still running single-core ( http://bsdstats.org/bt/cpus.html ) ? René ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet escribió: > bsdstats.org > ports stats would have that information probably http://bsdstats.org/ports.php?category=91 says in column 'times in use': x11/kde3: 534 x11/kde4: 86 matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
bsdstats.org > ports stats would have that information probably Here, I've installed snotes, xxdiff and a few others (qt33...) not kde3 per se... Subject: Re: kde3 ports expired today Are there any numbers how many FreeBSD(!) users are using KDE3 or KDE4? If not, what about a well organized(!) straw poll? Just to see, if we are all hunting in the right direction. matthias - ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On 07/01/13 16:40, Matthias Apitz wrote: El día Monday, July 01, 2013 a las 10:26:13PM +0200, Per olof Ljungmark escribió: While I have full respect for this decision I am another example of one that looses his desktop... Actually, I'm not really using KDE3, but rather xfce but with the apps from KDE3 like konsole, kwrite, ksnapshot and a few others that I failed to see any good replacements for. And security, well, not sure if this is that important for a desktop? At least we're warned. And KDE4 is not an alternative, tried several times but gave up. Are there any numbers how many FreeBSD(!) users are using KDE3 or KDE4? If not, what about a well organized(!) straw poll? Just to see, if we are all hunting in the right direction. matthias I currently use KDE3, I never liked the direction KDE4 took. I did contemplate porting Trinity over to FreeBSD, but I never really had the time to do it, mainly because of how they are so scattered on how to build it (plus their build instructions are haphazard at best). Even though the ports have expired, I'll probably continue to use KDE3 on my desktop. Thanks, Naram Qashat ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
El día Monday, July 01, 2013 a las 10:26:13PM +0200, Per olof Ljungmark escribió: > While I have full respect for this decision I am another example of one > that looses his desktop... > > Actually, I'm not really using KDE3, but rather xfce but with the apps > from KDE3 like konsole, kwrite, ksnapshot and a few others that I failed > to see any good replacements for. > > And security, well, not sure if this is that important for a desktop? At > least we're warned. > > And KDE4 is not an alternative, tried several times but gave up. Are there any numbers how many FreeBSD(!) users are using KDE3 or KDE4? If not, what about a well organized(!) straw poll? Just to see, if we are all hunting in the right direction. matthias -- Sent from my FreeBSD netbook Matthias Apitz, , http://www.unixarea.de/ f: +49-170-4527211 UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On 2013-07-01 11:38, Baptiste Daroussin wrote: > On Mon, Jul 01, 2013 at 10:20:22AM +0200, Matthias Apitz wrote: >> El día Monday, July 01, 2013 a las 09:59:48AM +0200, René Ladan escribió: >> >>> Hi, >>> >>> the KDE3 ports (263 of them) expired today. They were marked for >>> removal since December 30, so the plan is to remove them soon. >>> >>> Regards, >>> Rene >> >> Hi, >> >> We have (perhaps) all seen this in UPDATING and while compiling qt3* >> ports; I think, it is not a good idea deleting the KDE3 ports (which do >> compile) from our ports tree, while the KDE4 ports do not compile, at >> least not on i386 architecture. See the PR's about automoc4 and others. >> >> Just my humble opinion >> >> matthias >> > > Problem is that kde3 is not maintained anymore upstream, not security reviews > are performed any more etc. It has been deprecated for 6 month, and no one > came > up to: > 1/ take maitainership of kde3 > 2/ import the maintained and supported trinity project. While I have full respect for this decision I am another example of one that looses his desktop... Actually, I'm not really using KDE3, but rather xfce but with the apps from KDE3 like konsole, kwrite, ksnapshot and a few others that I failed to see any good replacements for. And security, well, not sure if this is that important for a desktop? At least we're warned. And KDE4 is not an alternative, tried several times but gave up. Just my two öre. //per ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] kde3 ports expired today
Matthias Apitz writes: > We have (perhaps) all seen this in UPDATING and while compiling qt3* > ports; I think, it is not a good idea deleting the KDE3 ports (which do > compile) from our ports tree, while the KDE4 ports do not compile, at > least not on i386 architecture. See the PR's about automoc4 and others. To be fair, the problem with the random automoc crashes seems to be specific to i386 on CURRENT (we do have binary packages for our released versions after all) and dim@ was already taking a look at that a few days ago. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
2013/7/1 Matthias Apitz : > El día Monday, July 01, 2013 a las 09:59:48AM +0200, René Ladan escribió: > >> the KDE3 ports (263 of them) expired today. They were marked for >> removal since December 30, so the plan is to remove them soon. >> > > We have (perhaps) all seen this in UPDATING and while compiling qt3* > ports; I think, it is not a good idea deleting the KDE3 ports (which do > compile) from our ports tree, while the KDE4 ports do not compile, at > least not on i386 architecture. See the PR's about automoc4 and others. > This looks like two different things to me, and maybe the absence of KDE3/QT3 will accelerate fixing KDE4/QT4 on i386 and other affected architectures. René ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3 ports expired today
On Mon, Jul 01, 2013 at 10:20:22AM +0200, Matthias Apitz wrote: > El día Monday, July 01, 2013 a las 09:59:48AM +0200, René Ladan escribió: > > > Hi, > > > > the KDE3 ports (263 of them) expired today. They were marked for > > removal since December 30, so the plan is to remove them soon. > > > > Regards, > > Rene > > Hi, > > We have (perhaps) all seen this in UPDATING and while compiling qt3* > ports; I think, it is not a good idea deleting the KDE3 ports (which do > compile) from our ports tree, while the KDE4 ports do not compile, at > least not on i386 architecture. See the PR's about automoc4 and others. > > Just my humble opinion > > matthias > Problem is that kde3 is not maintained anymore upstream, not security reviews are performed any more etc. It has been deprecated for 6 month, and no one came up to: 1/ take maitainership of kde3 2/ import the maintained and supported trinity project. regards, Bapt pgpafB2fpOfKe.pgp Description: PGP signature
Re: kde3 ports expired today
El día Monday, July 01, 2013 a las 09:59:48AM +0200, René Ladan escribió: > Hi, > > the KDE3 ports (263 of them) expired today. They were marked for > removal since December 30, so the plan is to remove them soon. > > Regards, > Rene Hi, We have (perhaps) all seen this in UPDATING and while compiling qt3* ports; I think, it is not a good idea deleting the KDE3 ports (which do compile) from our ports tree, while the KDE4 ports do not compile, at least not on i386 architecture. See the PR's about automoc4 and others. Just my humble opinion matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
kde3 ports expired today
Hi, the KDE3 ports (263 of them) expired today. They were marked for removal since December 30, so the plan is to remove them soon. Regards, Rene ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
KDE3 && qt33 in ports
Hello, I'm still an active user of KDE3, compiling from ports, at the moment from SVN r315646; the ports Makefile say that the port will be removed as of July 1st 2013 which would let me w/o my desktop. I will not switch to KDE4 because this is an overkill for my FreeBSD netbook (EeePC 900) and I do not need all this plasma and other coloured stuff. Is it really so hard to keep KDE3 and qt33 in the ports tree and just adjust from time to time, if required, some dependencies? As I said, at the moment it is just compiling fine with 'make install BATCH=yes' in ports/x11/kde3. If there is helping hand required, I could do so if this fits with my knowledge. Please let us keep KDE3 / qt33 in the ports. Thanks matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
I was thinking of December patches. Till now, each time kde3 broke, in few weeks someone would sent patch. > A few clicks leads to nice UI experience with roughly the same > amount of overheard as the 3.x I simply do not believe that. Stripped (!) KDE3 is workable on PIII system, to think the same of KDE4 with much heavier Qt and default configuration would be really stretching plausibility... In the end, I do not care enough (or even like KDE) to support KDE3, but I understand some of the concerns, as I was supporting one KDE3 system, where I wouldn't even try to change to KDE4. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Why-delete-KDE3-ports-tp5775510p5776226.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 09.01.2013 14:53, Adam Vande More wrote: I don't use knotes, but have you tried the solution here? http://forum.kde.org/viewtopic.php?f=22&t=84823 Obviously, knotes was just an example. All other customizations (such as menus, backgrounds&screen-savers, email accounts -- everything under ~/.kde) have to be redone too and, frankly, I do not trust today's KDE project to not do the same nonsense again, when they decide to abandon KDE4 for 5 (can't be long now that the release is 4.8). The very existence of the project Trinity is a sign, that my opinion is shared by a few more people. This can all be handled, but meanwhile, until there ARE actual problems, leave the ports alone, please. "Actual problems" have already been cited for it. No, they have not. The minor security threat cited is easily managed by simply not using kdm on a system, where less than trusted users have access. kdm is a minor part of KDE anyway (I, for one, use xdm). Fighting change can often lead much more wasted Yes, it often can. But not in this case. Yours, -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On Wed, Jan 9, 2013 at 8:07 AM, Mikhail T. wrote: > Worse, KDE4 is not only much heavier (which could've been acceptable). This is simply not true, or at least easily remediable. A few clicks leads to nice UI experience with roughly the same amount of overheard as the 3.x series. There are a number of quasi-legit investigations into the matter. Regardless of those methodologies, at the end of the day KDE4 requires only slightly more memory than 3 if at all. > It is also not compatible -- people like myself, who customized their > desktops with additional menus, who created knotes, etc. will have to redo > all of their settings. KDE4, as built, is not even going to look under the > ~/.kde. Though it can be compiled to consider the old directory, the > format/syntax for many of the config-files has changed -- and there is no > "upgrade path". I don't use knotes, but have you tried the solution here? http://forum.kde.org/viewtopic.php?f=22&t=84823 > This can all be handled, but meanwhile, until there ARE actual problems, > leave the ports alone, please. "Actual problems" have already been cited for it. Fighting change can often lead much more wasted effort than simply adjusting to modern offerings. It's easy enough to pull the port out of archive for the small amount of users who will insist on using a deprecated DE with known security issues. I don't think it reflects well on the project to continue to offer this as an option, and IMO at the very least needs to come with a blinking red light disclaimer if the port continues to exist. Jakub Lach: > In spite of not having 'proper' maintainer both kdelibs3/ and kdebas3/ saw substantial interest in form of patches Not recently, unless you mean bulk patches for patches to options framework, clang, or some other general change such as http://svnweb.freebsd.org/ports?view=revision&revision=297915 -- Adam Vande More ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
> tQT Well, presumable to not use it with not maintained, old vanilla QT In spite of not having 'proper' maintainer both kdelibs3/ and kdebas3/ saw substantial interest in form of patches, that indicates there are more people who care about them, than those taking voice in this thread... -- View this message in context: http://freebsd.1045724.n5.nabble.com/Why-delete-KDE3-ports-tp5775510p5776156.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 08.01.2013 19:02, Jakub Lach wrote: I'm on the fence. It's true, that there is no low-print feature complete equivalent for KDE3. Worse, KDE4 is not only much heavier (which could've been acceptable). It is also not compatible -- people like myself, who customized their desktops with additional menus, who created knotes, etc. will have to redo all of their settings. KDE4, as built, is not even going to look under the ~/.kde. Though it can be compiled to consider the old directory, the format/syntax for many of the config-files has changed -- and there is no "upgrade path". On the other hand, if nobody wants to maintain Trinity, well it should be letten go, as sooner or later there will be problems. Before becoming "maintained", Trinity first needs to be ported -- a substantial effort, because, for example, the project switched to its own verstion Qt (Trinity Qt). All classes have been renamed from Qfoo to TQfoo... This can all be handled, but meanwhile, until there ARE actual problems, leave the ports alone, please. -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
I'm on the fence. It's true, that there is no low-print feature complete equivalent for KDE3. On the other hand, if nobody wants to maintain Trinity, well it should be letten go, as sooner or later there will be problems. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Why-delete-KDE3-ports-tp5775510p5775952.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
John Marino writes: > On 1/8/2013 21:14, Raphael Kubo da Costa wrote: >> Additionally, I'd argue that it is hard for it to be "known insecure" >> since upstream does not maintain it even for security vulnerabilities >> anymore, so security problems have nowhere to be reported and >> vulnerabilities common to KDE3 and KDE4 only get published and fixed in >> the latter. > > This doesn't count? > http://cve.mitre.org/cve/ > http://web.nvd.nist.gov/view/vuln/search?execution=e2s1 > > It seems to be there is somewhere to report them... The vulnerabilities disclosed in those places are normally published after upstream has been contacted and come up with a fix for the security issue, so I don't think the lack of new KDE3 advisories compared to KDE4 ones means the former is safer. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 1/8/2013 21:14, Raphael Kubo da Costa wrote: Adam Vande More writes: On Mon, Jan 7, 2013 at 12:53 PM, John Marino wrote: "possibly insecure": I think this needs to be "known insecure" rather than holding it's last release date against it. http://www.kde.org/info/security/advisory-20100413-1.txt Probably other security issues as well. I didn't have to look very long. In a codebase as large as KDE's, it seems a very slim chance indeed years could go by without maintenance and still maintain security. Additionally, I'd argue that it is hard for it to be "known insecure" since upstream does not maintain it even for security vulnerabilities anymore, so security problems have nowhere to be reported and vulnerabilities common to KDE3 and KDE4 only get published and fixed in the latter. This doesn't count? http://cve.mitre.org/cve/ http://web.nvd.nist.gov/view/vuln/search?execution=e2s1 It seems to be there is somewhere to report them... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
Adam Vande More writes: > On Mon, Jan 7, 2013 at 12:53 PM, John Marino wrote: >> "possibly insecure": I think this needs to be "known insecure" rather >> than holding it's last release date against it. > > http://www.kde.org/info/security/advisory-20100413-1.txt > > Probably other security issues as well. I didn't have to look very long. > In a codebase as large as KDE's, it seems a very slim chance indeed years > could go by without maintenance and still maintain security. Additionally, I'd argue that it is hard for it to be "known insecure" since upstream does not maintain it even for security vulnerabilities anymore, so security problems have nowhere to be reported and vulnerabilities common to KDE3 and KDE4 only get published and fixed in the latter. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On Mon, Jan 7, 2013 at 12:49 PM, Adam Vande More wrote: > On Mon, Jan 7, 2013 at 12:53 PM, John Marino wrote: > >> >> Here's the issue I think some folks have: >> >> "Outdated": debatable. If outdated means a newer release is available, >> then yes. If "outdated" means it outlived its usefulness, I'd say no. This >> term seems subjectively used here. >> >> "prone to break": Perhaps, but it's not broken now. >> >> "possibly insecure": I think this needs to be "known insecure" rather >> than holding it's last release date against it. > > > http://www.kde.org/info/security/advisory-20100413-1.txt > > Probably other security issues as well. I didn't have to look very long. > In a codebase as large as KDE's, it seems a very slim chance indeed years > could go by without maintenance and still maintain security. I have a friend still happily using fvwm (not fvwm2). It is really, really old, but it still works. It is not subject to deletion because it still has a maintainer. Being a maintainer of a port that is not in active development is really not hard if you use it and can test it. I don't use KDE3, but someone who does can certainly become maintainer and it won't go away. If no one cares enough about keeping the port to take over maintainership, "Say la vee". (For the record, the last real change to fvwm was almost 4 years ago.) -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On Mon, Jan 7, 2013 at 12:53 PM, John Marino wrote: > > Here's the issue I think some folks have: > > "Outdated": debatable. If outdated means a newer release is available, > then yes. If "outdated" means it outlived its usefulness, I'd say no. This > term seems subjectively used here. > > "prone to break": Perhaps, but it's not broken now. > > "possibly insecure": I think this needs to be "known insecure" rather > than holding it's last release date against it. http://www.kde.org/info/security/advisory-20100413-1.txt Probably other security issues as well. I didn't have to look very long. In a codebase as large as KDE's, it seems a very slim chance indeed years could go by without maintenance and still maintain security. -- Adam Vande More ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 1/7/2013 19:40, Beat Gaetzi wrote: On 01/07/13 15:22, Mikhail T. wrote: Once again a working port (no build errors) is scheduled for deletion on the grounds of simply being "unmaintained". QT 3.3.8 was released in 2007 and KDE 3.5.10 in 2008 and both are no longer maintained upstream nor in the ports tree. They possibly contain security vulnerabilities and they likely will break in the future if a build or lib dependency gets updated as they assume a 5 year old environment. The deprecation period was set to 6 month to give someone the opportunity to update QT3 and KDE3 to the Trinity fork and I'm happy to offer exp-runs (once the clusters are back) if someone has patches but I don't see a reason why we should keep pointyhat busy (during exp-runs and frequent QA runs) with something that is outdated and mostly unmaintained for years now, prone to break and possibly insecure. Here's the issue I think some folks have: "Outdated": debatable. If outdated means a newer release is available, then yes. If "outdated" means it outlived its usefulness, I'd say no. This term seems subjectively used here. "prone to break": Perhaps, but it's not broken now. "possibly insecure": I think this needs to be "known insecure" rather than holding it's last release date against it. So currently it's not broken, not known to be insecure, and it's probably still useful. I know I'd feel better if this discussion were taking place after a breakage due to a updated dependency or a realistically unpatchable vulnerability was discovered. John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 01/07/13 15:22, Mikhail T. wrote: > On 07.01.2013 03:33, freebsd-ports-requ...@freebsd.org wrote: >> portname: accessibility/kdeaccessibility description: >> Accessibility applications for KDE maintainer:po...@freebsd.org >> deprecated because: Depends on QT3; unmaintained expiration date: >> 2013-07-01 build errors: none. >> overview:http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=kdeaccessibility >> > >> Once again a working port (no build errors) is scheduled for deletion on > the grounds of simply being "unmaintained". QT 3.3.8 was released in 2007 and KDE 3.5.10 in 2008 and both are no longer maintained upstream nor in the ports tree. They possibly contain security vulnerabilities and they likely will break in the future if a build or lib dependency gets updated as they assume a 5 year old environment. The deprecation period was set to 6 month to give someone the opportunity to update QT3 and KDE3 to the Trinity fork and I'm happy to offer exp-runs (once the clusters are back) if someone has patches but I don't see a reason why we should keep pointyhat busy (during exp-runs and frequent QA runs) with something that is outdated and mostly unmaintained for years now, prone to break and possibly insecure. Beat > Please, reconsider deleting this and other KDE-3 ports. > > -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 01/07/13 15:43, John Marino wrote: I don't normally agree with Mikhail's rants to save old ports, but in the case of KDE-3, I am inclined to share his view. Are KDE-3 ports causing any problems? I don't know if KDE-3 is still be developed upstream, but if it's not it doesn't really need much maintenance. I fully agree with both statements. bye av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
Quoting "Mikhail T." : On 07.01.2013 09:54, Kimmo Paasiala wrote: Are you willing to step up as the maintainer of the KDE3 ports? Or anyone else reading this? The situation with ports like KDE3 is that they are lots of work to keep up in shape and if no one wants to maintain them they succumb to what is called "bitrot" very quickly when something changes in dependent ports or in the base system. When/if that happens, we can renew the conversation. For the time being there are no build errors. Indeed. That a port is old is not a good reason to remove it. That a port is unmaintained is also not a good reason to remove it. If a port stops working and nobody steps up to fix it, *then* removal becomes a reasonable action, but not before that. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 1/7/2013 16:04, Mikhail T. wrote: On 07.01.2013 09:54, Kimmo Paasiala wrote: Are you willing to step up as the maintainer of the KDE3 ports? Or anyone else reading this? The situation with ports like KDE3 is that they are lots of work to keep up in shape and if no one wants to maintain them they succumb to what is called "bitrot" very quickly when something changes in dependent ports or in the base system. When/if that happens, we can renew the conversation. For the time being there are no build errors. I agree with this. Simple bitrot can be patched pretty quickly even w/o a maintainer and if nobody is willing to do that then sure, kill it. FYI I already maintain a number of ports and I intend to add more Ada ports in the future, so I can't pick up KDE3 myself. John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 07.01.2013 09:54, Kimmo Paasiala wrote: Are you willing to step up as the maintainer of the KDE3 ports? Or anyone else reading this? The situation with ports like KDE3 is that they are lots of work to keep up in shape and if no one wants to maintain them they succumb to what is called "bitrot" very quickly when something changes in dependent ports or in the base system. When/if that happens, we can renew the conversation. For the time being there are no build errors. -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On Mon, Jan 7, 2013 at 4:43 PM, John Marino wrote: > On 1/7/2013 15:22, Mikhail T. wrote: >> >> On 07.01.2013 03:33, freebsd-ports-requ...@freebsd.org wrote: >>> >>> portname: accessibility/kdeaccessibility >>> description: Accessibility applications for KDE >>> maintainer:po...@freebsd.org >>> deprecated because: Depends on QT3; unmaintained >>> expiration date: 2013-07-01 >>> build errors: none. >>> >>> overview:http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=kdeaccessibility >>> >> Once again a working port (no build errors) is scheduled for deletion on >> the grounds of simply being "unmaintained". >> >> Please, reconsider deleting this and other KDE-3 ports. > > > I don't normally agree with Mikhail's rants to save old ports, but in the > case of KDE-3, I am inclined to share his view. > > Are KDE-3 ports causing any problems? I don't know if KDE-3 is still be > developed upstream, but if it's not it doesn't really need much maintenance. > > John > I'm asking this on behalf of the port maintainers so they don't have to. I'm not a committer nor a maintainer of any ports myself fyi. Are you willing to step up as the maintainer of the KDE3 ports? Or anyone else reading this? The situation with ports like KDE3 is that they are lots of work to keep up in shape and if no one wants to maintain them they succumb to what is called "bitrot" very quickly when something changes in dependent ports or in the base system. -Kimmo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 07.01.2013 09:41, David Demelier wrote: Because Qt3 is old and KDE3 will completely disappear. This is exactly the sentiment I find disagreeable -- that simply being "old" is enough to condemn a perfectly functional piece of software. Maybe, it is because of my own age, that I am -- in the back of my mind -- becoming concerned, the sentiment may get applied to humans as well. But, more likely, it is simply because it does not make sense... I think you should look at trinity. It is a fork of KDE3 and is in development to be ported to Qt4 :) Yes, I looked at it, and may even port it some day -- if I find a collaborator or two. In my opinion, absent the other "prong", Trinity is not even a "fork", but the actual next version of KDE3 (something, KDE4 is not). But, until then, deleting KDE3 ports -- which continue to build fine -- seems wrong. -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
On 1/7/2013 15:22, Mikhail T. wrote: On 07.01.2013 03:33, freebsd-ports-requ...@freebsd.org wrote: portname: accessibility/kdeaccessibility description: Accessibility applications for KDE maintainer:po...@freebsd.org deprecated because: Depends on QT3; unmaintained expiration date: 2013-07-01 build errors: none. overview:http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=kdeaccessibility Once again a working port (no build errors) is scheduled for deletion on the grounds of simply being "unmaintained". Please, reconsider deleting this and other KDE-3 ports. I don't normally agree with Mikhail's rants to save old ports, but in the case of KDE-3, I am inclined to share his view. Are KDE-3 ports causing any problems? I don't know if KDE-3 is still be developed upstream, but if it's not it doesn't really need much maintenance. John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why delete KDE3 ports?
Because Qt3 is old and KDE3 will completely disappear. It the same goal for GNOME 2 (not for now because GNOME 3 is not yet available) but GNOME 2 will ne probably replaced by MATE. I think you should look at trinity. It is a fork of KDE3 and is in development to be ported to Qt4 :) http://mate-desktop.org/ http://www.trinitydesktop.org/ 2013/1/7 Mikhail T. > On 07.01.2013 03:33, > freebsd-ports-request@freebsd.**orgwrote: > >> portname: accessibility/kdeaccessibility >> description:Accessibility applications for KDE >> maintainer:po...@freebsd.org >> deprecated because: Depends on QT3; unmaintained >> expiration date:2013-07-01 >> build errors: none. >> overview:http://portsmon.**FreeBSD.org/portoverview.py?** >> category=accessibility&**portname=kdeaccessibility<http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=kdeaccessibility> >> > Once again a working port (no build errors) is scheduled for deletion on > the grounds of simply being "unmaintained". > > Please, reconsider deleting this and other KDE-3 ports. > >-mi > > __**_ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-ports<http://lists.freebsd.org/mailman/listinfo/freebsd-ports> > To unsubscribe, send any mail to > "freebsd-ports-unsubscribe@**freebsd.org > " > -- Demelier David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Why delete KDE3 ports?
On 07.01.2013 03:33, freebsd-ports-requ...@freebsd.org wrote: portname: accessibility/kdeaccessibility description:Accessibility applications for KDE maintainer:po...@freebsd.org deprecated because: Depends on QT3; unmaintained expiration date:2013-07-01 build errors: none. overview:http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=kdeaccessibility Once again a working port (no build errors) is scheduled for deletion on the grounds of simply being "unmaintained". Please, reconsider deleting this and other KDE-3 ports. -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On Thu, May 31, 2012 at 6:52 PM, Per olof Ljungmark wrote: > BTW, if KDE3 is unmaintained and this gous for FreeBSD too, perhaps it > should be mentioned in the Handbook? I submitted these lines for the Handbook some time ago: There are two versions of KDE available on FreeBSD. Version 3 has been around for a long time, and is still available in the Ports Collection though it's now unmaintained and partially broken. Version 4 is punctually updated and is the default choice for KDE users. They can even be installed side by side. I think they're enough. -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On 31 May 2012 23:26, Etienne Robillard wrote: > On 05/31/2012 05:27 PM, Chris Rees wrote: >> >> On 31 May 2012 17:52, Per olof Ljungmark wrote: >>> >>> On 05/31/12 14:16, Chris Rees wrote: >>>> >>>> >>>> On May 31, 2012 12:39 PM, "Per olof Ljungmark" >>>> wrote: >>>>> >>>>> >>>>> >>>>> I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying >>>>> to >>>> >>>> >>>> stick to KDE3. >>>>> >>>>> >>>>> >>>> >>>> Just a reminder that although people may try to help you, kde3 is >>>> unmaintained. >>> >>> >>> >>> BTW, if KDE3 is unmaintained and this gous for FreeBSD too, perhaps it >>> should be mentioned in the Handbook? >>> >> >> There is very little software that is unmaintained upstream and is >> maintained here-- it is strongly discouraged. Such a declaration >> would be therefore redundant; EOL upstream means unsupported in >> FreeBSD. >> >> Chris > > > Hi Chris, > > I don't know really for kde3-network specifically but I managed to compile > on a kde-lite without much problems on 8-STABLE after having deleted openssl > port. > > As for whether it is unmaintained, as long its not broken, I don't see > a reason to fix it unless you have specific needs for kde4... Of course-- my point was that a note in the Handbook should be unnecessary-- if it's EOL upstream then it is almost certainly not maintained or supported here. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On 05/31/2012 05:27 PM, Chris Rees wrote: On 31 May 2012 17:52, Per olof Ljungmark wrote: On 05/31/12 14:16, Chris Rees wrote: On May 31, 2012 12:39 PM, "Per olof Ljungmark"wrote: I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to stick to KDE3. Just a reminder that although people may try to help you, kde3 is unmaintained. BTW, if KDE3 is unmaintained and this gous for FreeBSD too, perhaps it should be mentioned in the Handbook? There is very little software that is unmaintained upstream and is maintained here-- it is strongly discouraged. Such a declaration would be therefore redundant; EOL upstream means unsupported in FreeBSD. Chris Hi Chris, I don't know really for kde3-network specifically but I managed to compile on a kde-lite without much problems on 8-STABLE after having deleted openssl port. As for whether it is unmaintained, as long its not broken, I don't see a reason to fix it unless you have specific needs for kde4... Cheers, 8-) Etienne -- Etienne Robillard Occupation: Software Developer Company:Green Tea Hackers Club Email: e...@gthcfoundation.org Website:gthcfoundation.org Skype ID: incidah ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On 31 May 2012 17:52, Per olof Ljungmark wrote: > On 05/31/12 14:16, Chris Rees wrote: >> >> On May 31, 2012 12:39 PM, "Per olof Ljungmark" wrote: >>> >>> >>> I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to >> >> stick to KDE3. >>> >>> >> >> Just a reminder that although people may try to help you, kde3 is >> unmaintained. > > > BTW, if KDE3 is unmaintained and this gous for FreeBSD too, perhaps it > should be mentioned in the Handbook? > There is very little software that is unmaintained upstream and is maintained here-- it is strongly discouraged. Such a declaration would be therefore redundant; EOL upstream means unsupported in FreeBSD. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On 05/31/12 14:16, Chris Rees wrote: On May 31, 2012 12:39 PM, "Per olof Ljungmark" wrote: I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to stick to KDE3. Just a reminder that although people may try to help you, kde3 is unmaintained. BTW, if KDE3 is unmaintained and this gous for FreeBSD too, perhaps it should be mentioned in the Handbook? Maybe I should file a PR... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On 05/31/12 14:32, Alberto Villa wrote: On Thu, May 31, 2012 at 2:24 PM, Per olof Ljungmark wrote: I heard from somewhere that there is a fork of KDE3 maintained by folks that just like me finds KDE4 unusable. Perhaps someone on the list knows more? http://www.trinitydesktop.org Ah, yes. But no available yet for us it seems? I for one would really like to see this ports... //per ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On Thu, May 31, 2012 at 2:24 PM, Per olof Ljungmark wrote: > I heard from somewhere that there is a fork of KDE3 maintained by folks that > just like me finds KDE4 unusable. Perhaps someone on the list knows more? http://www.trinitydesktop.org -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On 2012-05-31 14:16, Chris Rees wrote: On May 31, 2012 12:39 PM, "Per olof Ljungmark" wrote: I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to stick to KDE3. Recent 9-STABLE amd64 Just a reminder that although people may try to help you, kde3 is unmaintained. Yes, I'm aware of this but unable to find a replacement that works for me. I am confident this error is fixable because I have another almost identical workstation at home with recent 9-STABLE amd64 where kdenetwork3 builds fine. I heard from somewhere that there is a fork of KDE3 maintained by folks that just like me finds KDE4 unusable. Perhaps someone on the list knows more? Thanks, ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kde3-network compile error, is this fixable?
On May 31, 2012 12:39 PM, "Per olof Ljungmark" wrote: > > I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to stick to KDE3. > > Recent 9-STABLE amd64 > > mv -f .deps/talkconn.Tpo .deps/talkconn.Po > rm -f libmach.a > ar cru libmach.a answmach.o forwmach.o talkconn.o > ranlib libmach.a > gmake[4]: Leaving directory `/usr/ports/net/kdenetwork3/work/kdenetwork-3.5.10/ktalkd/ktalkd/machines' > gmake[4]: Entering directory `/usr/ports/net/kdenetwork3/work/kdenetwork-3.5.10/ktalkd/ktalkd' > cc -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -DNDEBUG -O2 -O2 -pipe -fno-strict-aliasing -MT print.o -MD -MP -MF .deps/print.Tpo -c -o print.o print.c > mv -f .deps/print.Tpo .deps/print.Po > cc -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -DNDEBUG -O2 -O2 -pipe -fno-strict-aliasing -MT repairs.o -MD -MP -MF .deps/repairs.Tpo -c -o repairs.o repairs.c > mv -f .deps/repairs.Tpo .deps/repairs.Po > c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT announce.o -MD -MP -MF .deps/announce.Tpo -c -o announce.o announce.cpp > mv -f .deps/announce.Tpo .deps/announce.Po > c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT process.o -MD -MP -MF .deps/process.Tpo -c -o process.o process.cpp > mv -f .deps/process.Tpo .deps/process.Po > c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT readcfg++.o -MD -MP -MF .deps/readcfg++.Tpo -c -o readcfg++.o readcfg++.cpp > mv -f .deps/readcfg++.Tpo .deps/readcfg++.Po > c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT table.o -MD -MP -MF .deps/table.Tpo -c -o table.o table.cpp > mv -f .deps/table.Tpo .deps/table.Po > c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT talkd.o -MD -MP -MF .deps/talkd.Tpo -c -o talkd.o talkd.cpp > mv -f .deps/talkd.Tpo .deps/talkd.Po > c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARG
kde3-network compile error, is this fixable?
I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to stick to KDE3. Recent 9-STABLE amd64 mv -f .deps/talkconn.Tpo .deps/talkconn.Po rm -f libmach.a ar cru libmach.a answmach.o forwmach.o talkconn.o ranlib libmach.a gmake[4]: Leaving directory `/usr/ports/net/kdenetwork3/work/kdenetwork-3.5.10/ktalkd/ktalkd/machines' gmake[4]: Entering directory `/usr/ports/net/kdenetwork3/work/kdenetwork-3.5.10/ktalkd/ktalkd' cc -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -DNDEBUG -O2 -O2 -pipe -fno-strict-aliasing -MT print.o -MD -MP -MF .deps/print.Tpo -c -o print.o print.c mv -f .deps/print.Tpo .deps/print.Po cc -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -DNDEBUG -O2 -O2 -pipe -fno-strict-aliasing -MT repairs.o -MD -MP -MF .deps/repairs.Tpo -c -o repairs.o repairs.c mv -f .deps/repairs.Tpo .deps/repairs.Po c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT announce.o -MD -MP -MF .deps/announce.Tpo -c -o announce.o announce.cpp mv -f .deps/announce.Tpo .deps/announce.Po c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT process.o -MD -MP -MF .deps/process.Tpo -c -o process.o process.cpp mv -f .deps/process.Tpo .deps/process.Po c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT readcfg++.o -MD -MP -MF .deps/readcfg++.Tpo -c -o readcfg++.o readcfg++.cpp mv -f .deps/readcfg++.Tpo .deps/readcfg++.Po c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT table.o -MD -MP -MF .deps/table.Tpo -c -o table.o table.cpp mv -f .deps/table.Tpo .deps/table.Po c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT talkd.o -MD -MP -MF .deps/talkd.Tpo -c -o talkd.o talkd.cpp mv -f .deps/talkd.Tpo .deps/talkd.Po c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu -I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1 -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -fno-strict-aliasing -Wno-non-vi
Re: [kde-freebsd] UPDATING 20111016 and KDE3
On Wed, Oct 19, 2011 at 3:07 PM, Raphael Kubo da Costa wrote: > Not sure I understood your question, but somehow /usr/local/qt4/include > must be added to the include path before /usr/local/include. No matter, I'll try to do it if you don't do it before. :) -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] UPDATING 20111016 and KDE3
Alberto Villa writes: > On Tue, Oct 18, 2011 at 8:46 PM, Raphael Kubo da Costa > wrote: >> I just need some free time to take a look at the issue, I suspect the >> fix can be done to a single place. >> >> But until then, feel free to set CONFLICTS_BUILD or something else :) > > Are you thinking about moving the KDE directories at the top? Or > something more sophisticated? Not sure I understood your question, but somehow /usr/local/qt4/include must be added to the include path before /usr/local/include. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] UPDATING 20111016 and KDE3
On Tue, Oct 18, 2011 at 8:46 PM, Raphael Kubo da Costa wrote: > I just need some free time to take a look at the issue, I suspect the > fix can be done to a single place. > > But until then, feel free to set CONFLICTS_BUILD or something else :) Are you thinking about moving the KDE directories at the top? Or something more sophisticated? -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] UPDATING 20111016 and KDE3
Alberto Villa writes: > On Tue, Oct 18, 2011 at 5:06 PM, Raphael Kubo da Costa > wrote: >> This seems to be a recurring issue. It looks like the qt3 includes in >> /usr/local/include get picked up before the qt4 ones in >> /usr/local/qt4/include. > > CONFLICTS_BUILD? I'm not sure we want to fix all those > include_directories()... I just need some free time to take a look at the issue, I suspect the fix can be done to a single place. But until then, feel free to set CONFLICTS_BUILD or something else :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] UPDATING 20111016 and KDE3
On Tue, Oct 18, 2011 at 5:06 PM, Raphael Kubo da Costa wrote: > This seems to be a recurring issue. It looks like the qt3 includes in > /usr/local/include get picked up before the qt4 ones in > /usr/local/qt4/include. CONFLICTS_BUILD? I'm not sure we want to fix all those include_directories()... -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] UPDATING 20111016 and KDE3
On Tue, Oct 18, 2011 at 5:06 PM, Raphael Kubo da Costa wrote: > This seems to be a recurring issue. It looks like the qt3 includes in > /usr/local/include get picked up before the qt4 ones in > /usr/local/qt4/include. CONFLICTS_BUILD? I'm not sure we want to fix all those include_directories()... -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] UPDATING 20111016 and KDE3
Rainer Hurling writes: > I had to deinstall qt-3.3.8_13, then install kdelibs4 (+ other kde4 > ports) and afterwards reinstall qt-3.3.8_13 again. This seems to be a recurring issue. It looks like the qt3 includes in /usr/local/include get picked up before the qt4 ones in /usr/local/qt4/include. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
Rainer Hurling schreef: I had to deinstall qt-3.3.8_13, then install kdelibs4 (+ other kde4 ports) and afterwards reinstall qt-3.3.8_13 again. Hope this helps, Rainer Hurling On 17.10.2011 12:51 (UTC+2), Leslie Jensen wrote: 2011-10-17 10:20, Andrea Venturoli skrev: On 10/17/11 10:08, Alberto Villa wrote: I've got another problem with this update! Kdelibs wont build. I followed the instructions in UPDATE. [ 56%] Building CXX object kio/CMakeFiles/kio.dir/kio/ksambasharedata.o [ 56%] Building CXX object kio/CMakeFiles/kio.dir/bookmarks/kbookmark.o In file included from /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:33: /usr/local/include/qdatetime.h:51: error: function definition does not declare parameters /usr/local/include/qdatetime.h:123: error: function definition does not declare parameters /usr/local/include/qdatetime.h:184: error: function definition does not declare parameters /usr/local/include/qdatetime.h:241: error: expected initializer before '&' token /usr/local/include/qdatetime.h:242: error: expected initializer before '&' token /usr/local/include/qdatetime.h:243: error: expected initializer before '&' token /usr/local/include/qdatetime.h:244: error: expected initializer before '&' token /usr/local/include/qdatetime.h:245: error: expected initializer before '&' token /usr/local/include/qdatetime.h:246: error: expected initializer before '&' token /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc: In member function 'void KBookmark::updateAccessMetadata()': /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:548: error: incomplete type 'QDateTime' used in nested name specifier *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/x11/kdelibs4. ===>>> make failed for x11/kdelibs4 ===>>> Aborting update I need help to solve this. Thanks /Leslie thanks for the pointer, for me as i could not build kdlibs4 also, deleting the qt-copy-3.3.8_13 port fixed it. I did not have the qt-3.3.8_13 port installed. regards Johan Hendriks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
I had to deinstall qt-3.3.8_13, then install kdelibs4 (+ other kde4 ports) and afterwards reinstall qt-3.3.8_13 again. Hope this helps, Rainer Hurling On 17.10.2011 12:51 (UTC+2), Leslie Jensen wrote: 2011-10-17 10:20, Andrea Venturoli skrev: On 10/17/11 10:08, Alberto Villa wrote: I've got another problem with this update! Kdelibs wont build. I followed the instructions in UPDATE. [ 56%] Building CXX object kio/CMakeFiles/kio.dir/kio/ksambasharedata.o [ 56%] Building CXX object kio/CMakeFiles/kio.dir/bookmarks/kbookmark.o In file included from /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:33: /usr/local/include/qdatetime.h:51: error: function definition does not declare parameters /usr/local/include/qdatetime.h:123: error: function definition does not declare parameters /usr/local/include/qdatetime.h:184: error: function definition does not declare parameters /usr/local/include/qdatetime.h:241: error: expected initializer before '&' token /usr/local/include/qdatetime.h:242: error: expected initializer before '&' token /usr/local/include/qdatetime.h:243: error: expected initializer before '&' token /usr/local/include/qdatetime.h:244: error: expected initializer before '&' token /usr/local/include/qdatetime.h:245: error: expected initializer before '&' token /usr/local/include/qdatetime.h:246: error: expected initializer before '&' token /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc: In member function 'void KBookmark::updateAccessMetadata()': /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:548: error: incomplete type 'QDateTime' used in nested name specifier *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/x11/kdelibs4. ===>>> make failed for x11/kdelibs4 ===>>> Aborting update I need help to solve this. Thanks /Leslie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
On Mon, 17 Oct 2011 20:13:30 +0200 Alberto Villa wrote: > On Mon, Oct 17, 2011 at 7:11 PM, Ion-Mihai Tetcu > wrote: > >> If you have both kdenetwork3 and 4, well, I don't know. You can try > >> proceeding with that step and seeing if kdenetwork3 still works, > >> and report back. I thought it was quite unlikely that people had > >> kdenetwork3 and 4 installed at the same time. Should this be a > >> problem, I'll end up making it optional in kdenetwork4. > > > > Please do, I have them both. > > I have some problems doing it at the moment. rakuco/makc, can you test > a fix for this? > > itetcu: did you try doing the replacement and seeing if kdenetwork3 > still works? No, I'll try sometime this week. -- IOnut ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
On Mon, Oct 17, 2011 at 7:11 PM, Ion-Mihai Tetcu wrote: >> If you have both kdenetwork3 and 4, well, I don't know. You can try >> proceeding with that step and seeing if kdenetwork3 still works, and >> report back. I thought it was quite unlikely that people had >> kdenetwork3 and 4 installed at the same time. Should this be a >> problem, I'll end up making it optional in kdenetwork4. > > Please do, I have them both. I have some problems doing it at the moment. rakuco/makc, can you test a fix for this? itetcu: did you try doing the replacement and seeing if kdenetwork3 still works? -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
On Mon, 17 Oct 2011 10:08:57 +0200 Alberto Villa wrote: > On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli > wrote: > > Using KDE3, I have ortp as a dependency of kdenetwork. > > Should I follow the above or is it ok only for KDE4? > > Is it needed? Would it harm anything? > > linphone-base is required by kdenetwork4, if you don't have it you can > skip that line. I'll add it to UPDATING, thanks. > > If you have both kdenetwork3 and 4, well, I don't know. You can try > proceeding with that step and seeing if kdenetwork3 still works, and > report back. I thought it was quite unlikely that people had > kdenetwork3 and 4 installed at the same time. Should this be a > problem, I'll end up making it optional in kdenetwork4. Please do, I have them both. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: UPDATING 20111016 and KDE3
2011/10/17 Leslie Jensen : > > > 2011-10-17 10:20, Andrea Venturoli skrev: >> >> On 10/17/11 10:08, Alberto Villa wrote: > > > > > I've got another problem with this update! Kdelibs wont build. > > I followed the instructions in UPDATE. > > > [ 56%] Building CXX object kio/CMakeFiles/kio.dir/kio/ksambasharedata.o > [ 56%] Building CXX object kio/CMakeFiles/kio.dir/bookmarks/kbookmark.o > In file included from > /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:33: > /usr/local/include/qdatetime.h:51: error: function definition does not > declare parameters > /usr/local/include/qdatetime.h:123: error: function definition does not > declare parameters > /usr/local/include/qdatetime.h:184: error: function definition does not > declare parameters > /usr/local/include/qdatetime.h:241: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:242: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:243: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:244: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:245: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:246: error: expected initializer before '&' > token > /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc: In > member function 'void KBookmark::updateAccessMetadata()': > /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:548: > error: incomplete type 'QDateTime' used in nested name specifier > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 1 > > Stop in /usr/ports/x11/kdelibs4. > > ===>>> make failed for x11/kdelibs4 > ===>>> Aborting update > > > I need help to solve this. > > Thanks > > /Leslie > > > > > > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > Just a me to, but my error is slightly different. /usr/local/include/qdatetime.h:51: error: function definition does not declare parameters /usr/local/include/qdatetime.h:123: error: function definition does not declare parameters /usr/local/include/qdatetime.h:184: error: function definition does not declare parameters /usr/local/include/qdatetime.h:241: error: expected initializer before '&' token /usr/local/include/qdatetime.h:242: error: expected initializer before '&' token /usr/local/include/qdatetime.h:243: error: expected initializer before '&' token /usr/local/include/qdatetime.h:244: error: expected initializer before '&' token /usr/local/include/qdatetime.h:245: error: expected initializer before '&' token /usr/local/include/qdatetime.h:246: error: expected initializer before '&' token /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc: In member function 'void KBookmark::updateAccessMetadata()': /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:548: error: incomplete type 'QDateTime' used in nested name specifier *** Error code 1 In file included from /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmarkimporter.cc:28: /usr/local/include/qtextcodec.h:51: error: function definition does not declare parameters /usr/local/include/qtextcodec.h:57: error: function definition does not declare parameters /usr/local/include/qtextcodec.h:63: error: function definition does not declare parameters /usr/local/include/qtextcodec.h:125: error: invalid use of incomplete type 'struct QTextCodec' /usr/local/include/qt4/QtCore/qstring.h:95: error: forward declaration of 'struct QTextCodec' /usr/local/include/qtextcodec.h:126: error: invalid use of incomplete type 'struct QTextCodec' /usr/local/include/qt4/QtCore/qstring.h:95: error: forward declaration of 'struct QTextCodec' /usr/local/include/qtextcodec.h:127: error: invalid use of incomplete type 'struct QTextCodec' /usr/local/include/qt4/QtCore/qstring.h:95: error: forward declaration of 'struct QTextCodec' /usr/local/include/qtextcodec.h:128: error: invalid use of incomplete type 'struct QTextCodec' /usr/local/include/qt4/QtCore/qstring.h:95: error: forward declaration of 'struct QTextCodec' *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/x11/kdelibs4. ===>>> make failed for x11/kdelibs4 ===>>> Aborting update ===>>> Update for x11/kdelibs4 failed ===>>> Aborting update ===>>> Update for multimedia/kdemultimedia4 failed ===>>> Aborting update after a portmaster -d -a regards Johan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
2011-10-17 10:20, Andrea Venturoli skrev: On 10/17/11 10:08, Alberto Villa wrote: I've got another problem with this update! Kdelibs wont build. I followed the instructions in UPDATE. [ 56%] Building CXX object kio/CMakeFiles/kio.dir/kio/ksambasharedata.o [ 56%] Building CXX object kio/CMakeFiles/kio.dir/bookmarks/kbookmark.o In file included from /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:33: /usr/local/include/qdatetime.h:51: error: function definition does not declare parameters /usr/local/include/qdatetime.h:123: error: function definition does not declare parameters /usr/local/include/qdatetime.h:184: error: function definition does not declare parameters /usr/local/include/qdatetime.h:241: error: expected initializer before '&' token /usr/local/include/qdatetime.h:242: error: expected initializer before '&' token /usr/local/include/qdatetime.h:243: error: expected initializer before '&' token /usr/local/include/qdatetime.h:244: error: expected initializer before '&' token /usr/local/include/qdatetime.h:245: error: expected initializer before '&' token /usr/local/include/qdatetime.h:246: error: expected initializer before '&' token /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc: In member function 'void KBookmark::updateAccessMetadata()': /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:548: error: incomplete type 'QDateTime' used in nested name specifier *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/x11/kdelibs4. ===>>> make failed for x11/kdelibs4 ===>>> Aborting update I need help to solve this. Thanks /Leslie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
On 10/17/11 10:08, Alberto Villa wrote: On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli wrote: Using KDE3, I have ortp as a dependency of kdenetwork. Should I follow the above or is it ok only for KDE4? Is it needed? Would it harm anything? linphone-base is required by kdenetwork4, if you don't have it you can skip that line. I'll add it to UPDATING, thanks. If you have both kdenetwork3 and 4, well, I don't know. You can try proceeding with that step and seeing if kdenetwork3 still works, and report back. I thought it was quite unlikely that people had kdenetwork3 and 4 installed at the same time. Should this be a problem, I'll end up making it optional in kdenetwork4. Thanks for the answer. In fact I have only kdenetwork3 and I don't plan on installing kdenetwork4 for the time being. So I'll just skip this step and stick with ortp. bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
On 10/17/11 10:08, Alberto Villa wrote: On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli wrote: Using KDE3, I have ortp as a dependency of kdenetwork. Should I follow the above or is it ok only for KDE4? Is it needed? Would it harm anything? linphone-base is required by kdenetwork4, if you don't have it you can skip that line. I'll add it to UPDATING, thanks. If you have both kdenetwork3 and 4, well, I don't know. You can try proceeding with that step and seeing if kdenetwork3 still works, and report back. I thought it was quite unlikely that people had kdenetwork3 and 4 installed at the same time. Should this be a problem, I'll end up making it optional in kdenetwork4. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli wrote: > Using KDE3, I have ortp as a dependency of kdenetwork. > Should I follow the above or is it ok only for KDE4? > Is it needed? Would it harm anything? linphone-base is required by kdenetwork4, if you don't have it you can skip that line. I'll add it to UPDATING, thanks. If you have both kdenetwork3 and 4, well, I don't know. You can try proceeding with that step and seeing if kdenetwork3 still works, and report back. I thought it was quite unlikely that people had kdenetwork3 and 4 installed at the same time. Should this be a problem, I'll end up making it optional in kdenetwork4. -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
UPDATING 20111016 and KDE3
Hello. I've seen UPDATING 20111016: having only a few bits of KDE4 left-over, I decided to clean them all, so I almost didn't need to mv and rm as reported. However, I'm a bit doubtful on: > portmaster -o net/linphone-base ortp Using KDE3, I have ortp as a dependency of kdenetwork. Should I follow the above or is it ok only for KDE4? Is it needed? Would it harm anything? bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
> Ah, Pearson! Whoops :( Hope he'll not get mad of me for misspelling his name if he sees it :) > > Well, there are even more "interesting" > ideas. > > http://trinity-devel.pearsoncomputing.net/?0::3095 That at least seems fun. For me. But not usefull at all, yes. > > PS. Porting to Qt4? > > "Stalled due to continual upstream Qt4 bugs and > extremely poor Qt4 performance" Which I've told on their mailing list about a year ago, with no reaction from any of developers or users. Thats good news, btw. I like it. Very much. > > http://www.trinitydesktop.org/wiki/bin/view/Developers/RoadMap ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
Ah, Pearson! Well, there are even more "interesting" ideas. http://trinity-devel.pearsoncomputing.net/?0::3095 PS. Porting to Qt4? "Stalled due to continual upstream Qt4 bugs and extremely poor Qt4 performance" http://www.trinitydesktop.org/wiki/bin/view/Developers/RoadMap -- View this message in context: http://freebsd.1045724.n5.nabble.com/KDE3-de-facto-EOL-Project-Trinity-tp4885362p4898252.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
On Wed, Oct 12, 2011 at 09:57:30AM -0700, Jakub Lach wrote: > <...> > > > I do not like the idea of Preston to > > rewrite KDE3 to Qt4 (see no profits & so on). > > Where that idea came from? > Is it Preston Brown's? I've meant Timoty Preston guy, who is the leader of trinityDE project. > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/KDE3-de-facto-EOL-Project-Trinity-tp4885362p4896214.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
Hello, I'm as well a happy user of KDE3 in all my laptops and even my small EeePC 900 netbook. I don't want to miss this, because I think KDE4 is hunting in wrong directions from the point of view of the end user. While this is a personal opinion, it turned out that KDE4 just did not work. I compiled in July based on SVN a 9-CURRENT and the ports KDE4 and Xorg (...) and the result was that the desktop screen gets mangeled in some situations; if someone needs the details, look for the thread Subject: [kde-freebsd] mixups in KDE4 display of certain windows in kde-free...@freebsd.org; So, I really don't know what to do if ports/x11/kde does not compile anymore in 9- or 10-CURRENT. It is sad matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ 200†-20††: 10 years war in Afghanistan. Stop it now! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
<...> > I do not like the idea of Preston to > rewrite KDE3 to Qt4 (see no profits & so on). Where that idea came from? Is it Preston Brown's? -- View this message in context: http://freebsd.1045724.n5.nabble.com/KDE3-de-facto-EOL-Project-Trinity-tp4885362p4896214.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
> Hello, > > -- Hi list! > Judging from latest commits, KDE3 moved > swiftly from "stall, but usable" to explicitly Im very interested in supporting KDE3 to live on FreeBSD But have a lack of any programming experience and so, so just Im scared of it. If anyone could take a lead or something, I will be there to contribute. Probably I will try to find some time to write the ports for Trinity DE, but I do not like the idea of Preston to rewrite KDE3 to Qt4 (see no profits & so on). > best regards, > - Jakub Lach > best regards, - Krutov Mikle ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
Well, Brendan Fabeny fixed qt33 and affected kde bits. Thanks! -- View this message in context: http://freebsd.1045724.n5.nabble.com/KDE3-de-facto-EOL-Project-Trinity-tp4885362p4892915.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
On Tue, 2011-10-11 at 16:32 +0400, Konstantin Tokarev wrote: > > 09.10.2011, 22:30, "Jakub Lach": > > Speaking of lightness, XFCE is memory hungry > > these days and Linux centric, and Fluxbox is > > not that light after all. > > Are you saying that Fluxbox is heavier than KDE3?? > > Especially when Fluxbox is a window manager and KDE is an desktop environment. Comparing those two on the same scale is like comparing FreeBSD to an ssh client. m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
09.10.2011, 22:30, "Jakub Lach": > Speaking of lightness, XFCE is memory hungry > these days and Linux centric, and Fluxbox is > not that light after all. Are you saying that Fluxbox is heavier than KDE3?? -- Regards, Konstantin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
I know, but neither is direct KDE3 replacement, nor does offer "complete user experience" (whatever it means, but I'm thinking of UI consistence mainly). Speaking of lightness, XFCE is memory hungry these days and Linux centric, and Fluxbox is not that light after all. I personally use dwm or mcwm, but it bears none relevance whatsoever. KDE3 was nice in that "DE which is not yet completely blown-out-of-proportions" way :) Thanks for attention. -- View this message in context: http://freebsd.1045724.n5.nabble.com/KDE3-de-facto-EOL-Project-Trinity-tp4885362p4885908.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
Op 09-10-2011 16:53, Jakub Lach schreef: > Hello, > > Judging from latest commits, KDE3 moved > swiftly from "stall, but usable" to explicitly > unsupported. > > However, there are still areas, where KDE3 > can't be replaced by newer version. > > (e.g. I maintain older pc that is mainly used > as internet browser, where I installed > slimmed subset of KDE3, to somehow make it > behave like users would expect. Looking > at state of KDE3 now, updating it borders > on "not worth breaking it".) > > [...] > I'm just saying, that if anyone would like > to still maintain a sane, slim subset of > KDE3, Project Trinity looks like good > starting point. http://trinitydesktop.org/ > There are also other lightweight desktop environments available in the ports tree, such as Xfce or fluxbox. -- http://www.rene-ladan.nl:8080/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 de facto EOL, Project Trinity?
On Sun, 9 Oct 2011 07:53:30 -0700 (PDT) Jakub Lach wrote: > Hello, > > Judging from latest commits, KDE3 moved > swiftly from "stall, but usable" to explicitly > unsupported. > > However, there are still areas, where KDE3 > can't be replaced by newer version. > > (e.g. I maintain older pc that is mainly used > as internet browser, where I installed > slimmed subset of KDE3, to somehow make it > behave like users would expect. Looking > at state of KDE3 now, updating it borders > on "not worth breaking it".) > > Of course I understand, that workforce > is limited, and everybody who is willing > to commit time, will spend it on their > pet-project. > > I'm just saying, that if anyone would like > to still maintain a sane, slim subset of > KDE3, Project Trinity looks like good > starting point. http://trinitydesktop.org/ > > KDE is-not-exactly my pet-project so > don't look at me :) > > best regards, > - Jakub Lach Hmmm, for some strange reason, I just heard a line from that old Elvis Presley song "Suspicious Minds" in my head: "Let's not let a good thing die..." :-) -- Conrad J. Sabatier conr...@cox.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
KDE3 de facto EOL, Project Trinity?
Hello, Judging from latest commits, KDE3 moved swiftly from "stall, but usable" to explicitly unsupported. However, there are still areas, where KDE3 can't be replaced by newer version. (e.g. I maintain older pc that is mainly used as internet browser, where I installed slimmed subset of KDE3, to somehow make it behave like users would expect. Looking at state of KDE3 now, updating it borders on "not worth breaking it".) Of course I understand, that workforce is limited, and everybody who is willing to commit time, will spend it on their pet-project. I'm just saying, that if anyone would like to still maintain a sane, slim subset of KDE3, Project Trinity looks like good starting point. http://trinitydesktop.org/ KDE is-not-exactly my pet-project so don't look at me :) best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/KDE3-de-facto-EOL-Project-Trinity-tp4885362p4885362.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/accessibility/kdeaccessibility Makefile ports/arabic/kde3-i18n Makefile ports/arabic/koffice-i18n Makefile ports/audio/arts Makefile ports/audio/juk Makefile ports/audio/mpeglib_
On Mon, Jul 11, 2011 at 08:51:02AM +1000, Peter Jeremy wrote: > It would be useful if there was a mechanism to warn users > that the port they are about to install (or have installed) is no > longer recommended. IMHO using DEPRECATED without EXPIRATION_DATE is just fine for this. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/accessibility/kdeaccessibility Makefile ports/arabic/kde3-i18n Makefile ports/arabic/koffice-i18n Makefile ports/audio/arts Makefile ports/audio/juk Makefile ports/audio/mpeglib_
On 2011-Jul-07 23:13:08 +0400, Max Brazhnikov wrote: >Until ports are not broken or/and forbidden I see no reason for deprecation >and removing them. >However you may consider this step as a recommendation to migrate from >Qt3/KDE3 ports to anything else. I would suggest that deprecation (without a specific expiry date) is a good way to issue that recommendation. I don't know of any recent cases but there have been past cases where people have unknowingly installed obsolete ports and then run into problems. It would be useful if there was a mechanism to warn users that the port they are about to install (or have installed) is no longer recommended. -- Peter Jeremy pgpffru4b21Mu.pgp Description: PGP signature
Re: [kde-freebsd] Re: KDE3 and Qt3 are not maintained anymore
On Fri, Jul 8, 2011 at 7:49 AM, Matthias Apitz wrote: > Max Brazhnikov wrote: > > > > The KDE FreeBSD team has officially dropped support for Qt3/KDE3 > > ports. We are not going to remove them in the near future, so > > you can continue to use them. But we strongly recommend you to > > consider alternative solutions. > > While I can understand that KDE3 is not developed further, I'm unhappy > to read that the support for the Qt3/KDE3 ports is dropped; I don't > expect bugs fixed in Qt3/KDE3 anymore, but at least the ports should be > able to compile and maybe adopted to changes in ports they depend on. > > KDE4 is in no way an alternative for smaller netbooks (like EeePC), > maybe not even for real workstations. > > KDE4, using the plasma-netbook shell, works beautifully on a 10.1" Asus eeePC 1005HA (Atom CPU, Intel graphics, 1 GB RAM). It's replaced my 15" laptop completely at work, and almost replaced my desktop at home due to the portability. It even runs acceptably well on an original Asus eeePC 701 with only 256 (or 512?) MB of RAM and a Celeron CPU, although an upgrade to X or the Intel graphics driver caused it to start flickering when opening, closing, or moving windows. Last time I tried it was with KDE 4.2 or 4.3. Shortly thereafter I got the 1005 above. -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] Re: KDE3 and Qt3 are not maintained anymore
Matthias Apitz writes: > Max Brazhnikov wrote: >> >> The KDE FreeBSD team has officially dropped support for Qt3/KDE3 >> ports. We are not going to remove them in the near future, so >> you can continue to use them. But we strongly recommend you to >> consider alternative solutions. > > While I can understand that KDE3 is not developed further, I'm unhappy > to read that the support for the Qt3/KDE3 ports is dropped; I don't > expect bugs fixed in Qt3/KDE3 anymore It's not that Qt3/KDE3 ports are being removed from the ports tree; the KDE on FreeBSD team is just officially stating that further work on maintaining these ports is not coming from us: nobody in the team has worked on or used Qt3+KDE3 for quite some time, so we prefer to focus our efforts on the current upstream versions. > but at least the ports should be able to compile and maybe adopted to > changes in ports they depend on. I think this has been done sort of automatically lately; when someone updates a port which has had its soversion the dependent ports are usually adjusted as well. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] Re: KDE3 and Qt3 are not maintained anymore
Max Brazhnikov wrote: > > The KDE FreeBSD team has officially dropped support for Qt3/KDE3 > ports. We are not going to remove them in the near future, so > you can continue to use them. But we strongly recommend you to > consider alternative solutions. While I can understand that KDE3 is not developed further, I'm unhappy to read that the support for the Qt3/KDE3 ports is dropped; I don't expect bugs fixed in Qt3/KDE3 anymore, but at least the ports should be able to compile and maybe adopted to changes in ports they depend on. KDE4 is in no way an alternative for smaller netbooks (like EeePC), maybe not even for real workstations. Thanks for your work in any case matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 and Qt3 are not maintained anymore
on 08/07/2011 13:30 Matthias Andree said the following: > Am 08.07.2011 06:25, schrieb Dima Panov: >> hello! >> >> 08.07.2011, 18:25, per...@pluto.rain.com: >>> Max Brazhnikov ; wrote: >>> >>>> The KDE FreeBSD team has officially dropped support for Qt3/KDE3 >>>> ports. We are not going to remove them in the near future, so >>>> you can continue to use them. But we strongly recommend you to >>>> consider alternative solutions. >>> >>> Can you recommend an alternative for kdiff3? >> >> for kde4 exist updated port, kdeff3-kde4 >> >> anyway, kde3 was dropped by kde.org some years ago. >> > > So, does kde4 have a certificate management tool in the meanwhile, or is > it still the same non-functional mock-up that shipped with KDE 4.0 back > then? > > I stopped trying at one point, I think I was fed up with that around KDE > 4.4... I think that it is better to direct your question (and possible frustration or suggestions) to official KDE communication channels, not to FreeBSD KDE _port_ maintainers. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 and Qt3 are not maintained anymore
Am 08.07.2011 06:25, schrieb Dima Panov: > hello! > > 08.07.2011, 18:25, per...@pluto.rain.com: >> Max Brazhnikov ; wrote: >> >>> The KDE FreeBSD team has officially dropped support for Qt3/KDE3 >>> ports. We are not going to remove them in the near future, so >>> you can continue to use them. But we strongly recommend you to >>> consider alternative solutions. >> >> Can you recommend an alternative for kdiff3? > > for kde4 exist updated port, kdeff3-kde4 > > anyway, kde3 was dropped by kde.org some years ago. > So, does kde4 have a certificate management tool in the meanwhile, or is it still the same non-functional mock-up that shipped with KDE 4.0 back then? I stopped trying at one point, I think I was fed up with that around KDE 4.4... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 and Qt3 are not maintained anymore
hello! 08.07.2011, 18:25, per...@pluto.rain.com: > Max Brazhnikov ; wrote: > >> The KDE FreeBSD team has officially dropped support for Qt3/KDE3 >> ports. We are not going to remove them in the near future, so >> you can continue to use them. But we strongly recommend you to >> consider alternative solutions. > > Can you recommend an alternative for kdiff3? for kde4 exist updated port, kdeff3-kde4 anyway, kde3 was dropped by kde.org some years ago. -- Dima Panov (flu...@freebsd.org) KDE@FreeBSD team Facebook: http://www.facebook.com/fluffy.khv ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 and Qt3 are not maintained anymore
per...@pluto.rain.com writes: > Max Brazhnikov wrote: > >> The KDE FreeBSD team has officially dropped support for Qt3/KDE3 >> ports. We are not going to remove them in the near future, so >> you can continue to use them. But we strongly recommend you to >> consider alternative solutions. > > Can you recommend an alternative for kdiff3? There's Kompare in kdesdk, but I don't know how it compares to kdiff3. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE3 and Qt3 are not maintained anymore
Max Brazhnikov wrote: > The KDE FreeBSD team has officially dropped support for Qt3/KDE3 > ports. We are not going to remove them in the near future, so > you can continue to use them. But we strongly recommend you to > consider alternative solutions. Can you recommend an alternative for kdiff3? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/accessibility/kdeaccessibility Makefile ports/arabic/kde3-i18n Makefile ports/arabic/koffice-i18n Makefile ports/audio/arts Makefile ports/audio/juk Makefile ports/audio/mpeglib_
On Jul 7, 2011, at 21:13 , Max Brazhnikov wrote: > On Thu, 07 Jul 2011 11:09:37 -0700, Doug Barton wrote: >> On 07/07/2011 10:21, Max Brazhnikov wrote: >>> Reset maintainership de jure. In fact KDE 3 has not been maintained by >>> our team >>> >>> for a long time, not to mention upstream. >>> >>> Discussed a while ago among the KDE/FreeBSD team. >> >> Certainly if the ports are not being maintained by kde@ then dropping >> maintainership is the right solution. However given the situation >> wouldn't deprecation+expiry be the logical next step? > > Until ports are not broken or/and forbidden I see no reason for deprecation > and removing them. Another reason to start the deprecation would be, that they are in the way of KDE4. So i think it is desirable to start deprecation. But last time i asked on this list a few months ago, there where still several users raising their interest, so maybe someone of them will step up in the next days.___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
