Re: Utility for safe updating of ports in base system
The real question is: ports or packages? Please do not mix them together! If we are talking about ports and ports updating then portmaster is (now) an excellent candidate for this job and I vote for portmaster. If we are talking about packages and package management then portmaster and all other ports updating tools are of course out of context. They are ports management tools - not - package management tools. So please change http://www.freebsd.org/projects/ideas/index.html#p-ports-upgrade The project idea is called 'Utility for safe updating of ports in base system'. The jobs description is false because of using 'pkg_*' but meaning 'port*'. And it really looks just like a request for rewrite portupgrade in C and to put this rewritten portupgrade in base. I strongly vote against it! The entry 'Package tools improvements' http://www.freebsd.org/projects/ideas/index.html#p-ports-pkgtools should be extended / rewritten for a new package management tool (/framework) idea. Michel Talon had described such a tool. So we are actually talking about two different things ... -- Regards, Sticky Bit <[EMAIL PROTECTED]> ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[KDE / QT FreeBSD users] CALL FOR HELPERS: Please contribute to the project! Thanks!
Dear KDE / QT on FreeBSD users, we need your help! Yes, -your- help! Why? Please read more ... I would not write this mail if everything was fine with KDE on FreeBSD. This is a gently but urgent request for help. Main problem is there are not enough contributors at the moment. This is really urgent because the whole 'KDE on FreeBSD' project is moving very slowly right now. This situation will not change until more users start to help us. Such a big task like porting and maintaining KDE on FreeBSD requires a huge amount of resources. But the project does not have enough responsive testers and contributors. We also need long term contributors and active maintainers. You asked yourself why there is no update of KDE 3 ports to latest stable 3.5.9 which were released months ago? You asked yourself why you are not able to dive into the exiting new world of KDE 4 on FreeBSD because there is no KDE 4 within FreeBSD ports tree yet? There are simply not enough contributors! You want these tasks to be done? Fine! But then please help. Only very few contributors are working on it at the moment. miwi@ is one of those. He did and does a very good job - also often in the background and not really noticed. He has already done a great work in porting KDE 4 to FreeBSD. But there is so much much more to do and he cannot do it all alone. If you have some free space on your disk, some time to spent and you are familiar with the ports tree then I ask you to contribute! No special skills required! First create a new user account just for testing purposes so your /home/.kde etc will not be touched when you run KDE 4. Checkout the area51 repository (see below). Then update QT4 first. Then build the KDE 4 ports you want. Log the builds and runtime tests of those ports. See http://wiki.freebsd.org/KDE4 for known problems. Report all (unknown) problems or bugs with full logs (e. g. post the logs at http://nopaste.unixfreunde.de/ ) and some details at [EMAIL PROTECTED] It is really that easy! You can do something like this: # cvs -d:ext:[EMAIL PROTECTED]:/home/kde-freebsd co area51 # mount -t unionfs /path/to/area51 /usr/ports Thanks to unionfs - which runs pretty well these days / RELENG7 - there is no risk for your original ports tree. Just do # umount /usr/ports and you can use it like before. Questions? Bug reports? Something else? Please subscribe to [EMAIL PROTECTED] at https://mail.kde.org/mailman/listinfo/kde-freebsd and mail your questions, answers, bugs, logs, etc. You can also search the archives. Remember: You can really help! Please contribute! You are very welcome! Thanks! Thanks! Thanks! -- Regards, Sticky Bit <[EMAIL PROTECTED]> ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xfce 4.4 RC1 - patchset 06
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, just applied your new patchset with a clean portstree and now getting new errors (patchset 05 worked fine for me). > - installation in LOCALBASE instead of X11BASE There are some problems with it. Stale leftovers under /usr/X11R6 directories and incompleted movements: 1.) Missing icons mentioned by xfce warning messages so I manually had to do # cp -r /usr/X11R6/share/icons/* /usr/local/share/icons # cp -r /usr/X11R6/share/pixmaps/* /usr/local/share/pixmaps 2.) I also noticed some disappearing apps in menu. So I had to do # cp -r /usr/X11R6/share/applications/* /usr/local/share/applications Now this - seems - to work as usual. But there are still much xfce leftovers (directories and files) under /usr/X11R6/ 3.) Now I got errors while trying to compile /misc/xfce4-weather-plugin and /deskutils/orage with patchset 06: a) xfce4-weather-plugin-0.5.99.1 cannot install: unknown component glib. Error code 1 Stop in ... Modified Makefile: changed 'glib' into 'glib20' and that did the trick. But then next error with both ports occured: b) libtool: link: cannot find the library '/usr/X11R6/lib/libxfcegui4.la' or unhandled argument '/usr/X11R6/lib/libxfcegui4.la' Error code 2 Stop in ... Could not try more for this morning. Bye -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFHKM7V3O5qMs3gsERCmOKAJ95GeDhVga3pugWPWEMIlujpIuNKACgr7hZ 1r5CgNG8DUaBqXFfP1F7yFM= =vofO -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xfce 4.4 RC1 - patchset 06
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > Are you sure you deinstalled all previous xfce components which where > installed below /usr/X11R6 in the past before installing the new ones? Deinstalled all xfce stuff using 'pkg_deinstall' then installed the new ones. I was sure all components were deinstalled but it seems I have missed something or something was not done right. Now I did it again using 'make deinstall clean' and I manually removed all old xfce leftovers in /usr/X11R6. Now double checked. Then really cleanly installed the new ones. And now ... it mostly seems to works. Sorry for any incommodities! Only the weather-plugin is not working: - - cannot update weather data Console message: ** (xfce4-weather-plugin:PID): WARNING **: Weather Plugin: No image found What could it be? Thanks! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFHLThV3O5qMs3gsERClnPAJoDhy6yxy/HCl/uL/vPB7b/0BP1+gCfYNbh ra5snrOpnjNHvaxM8P6nKvg= =Xdwi -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Thank you for portmaster
Hello, first let me thank you for developing such a nice tool! After so long time using portupgrade I gave portmaster a chance to convince me in daily usage. Now I am very happy with this decision and I begin to really like portmaster. One feature I would like to see implemented is a switch 'list only ports that have available updates'. I want to know all affected ports in summary before the builds so I am able to make decisions (i.e. 'portmaster -a' or just 'portmaster port', and think of the 'devel/gettext' update or other huge / long builds like gnome / gtk+ etc.). I am aware of the '-L' switch and the possibility to grep such ports. But this is a bit odd and not very likable. I want a similar output like 'portversion -vL=', i.e. port name along with old and new version numbering but only for ports with a different version available than installed (can also be an older version, think of a manually modified ports tree). Could you please add this small feature? Then I am actually able to do without portupgrade and its other tools. Thank you in advance! -- Kind regards, Sticky Bit *** True standards compliant plain text emails preferred. *** ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Thank you for portmaster
> Read the man pages for pkg_info, pkg_add, pkg_version, and pkg_delete, to > see all the things you can do with the ports/packages system. Those, > combined with portmaster, make for an excellent little ports toolkit. I am using FreeBSD for several years. I really know these tools very well and I already know what I want. They are part of my daily usage. So no help needed. ;-) Maybe you did not understand my intention. It is not a matter of what can be done with other tools but what can be done with portmaster. It was only a feature suggestion to improve portmaster not a request for help. Hope that makes it clear ... -- Kind regards, Sticky Bit *** True standards compliant plain text emails preferred. *** ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
