i keep *trying* to move from portupgrade to portmaster
I've been using ports-mgmt/portupgrade pretty much ever since it started to exist. Unfortunately portupgrade seems to be pretty much abandonware so I've been told to move on to portmaster. Despite the very long manpage I can't seem to be able to achieve the following thing with portmaster: $ portupgrade --batch -a If I issue this command I know exactly that I can go out, have a drink, cook some dinner and unlock my workstation the next day and find that everything completed unless a port failed to build. With portmaster I get asked a s*t load of interactive questions, whether I want to delete some package, whether it's really okay to pull in all the dependencies and so on. Can someone spoonfeed me the command I need to issue with portmaster in order to achieve the same thing as with $ portupgrade --batch -a Is that even possible? $ portupgrade --batch -a Thanks in advance! Sandra ___ 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: i keep *trying* to move from portupgrade to portmaster
On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer schweizer.mar...@gmail.com wrote: Hello Sandra I was in a similar situation. I found the following paramters very usefull: portmaster -a -d --no-confirm -a: Take all installed ports -d: Delete any dependicies -no--confirm: Wait not after the check which ports are upgradable With the above switch portmaster waits in two case: 1. If you run in an compile error 2. If the port is new and will asks you about make config I did now three upgrades like above and it worked as expected. Hi Martin Thank you for your answer (and everyone else who replied). This is exactly the reason why I keep going back to portupgrade. Default OPTIONS almost always work for me - if not I go to the ports directory and run make config then let the --batch option of portinstall deal with everything. It would be extremely nice if there would be a --batch option that would act like portupgrade. Sandra ___ 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: i keep *trying* to move from portupgrade to portmaster
On Fri, Aug 6, 2010 at 2:44 PM, Sandra Kachelmann s.kachelm...@googlemail.com wrote: On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer schweizer.mar...@gmail.com wrote: Hello Sandra I was in a similar situation. I found the following paramters very usefull: portmaster -a -d --no-confirm -a: Take all installed ports -d: Delete any dependicies -no--confirm: Wait not after the check which ports are upgradable With the above switch portmaster waits in two case: 1. If you run in an compile error 2. If the port is new and will asks you about make config I did now three upgrades like above and it worked as expected. Hi Martin Thank you for your answer (and everyone else who replied). This is exactly the reason why I keep going back to portupgrade. Default OPTIONS almost always work for me - if not I go to the ports directory and run make config then let the --batch option of portinstall deal with everything. It would be extremely nice if there would be a --batch option that would act like portupgrade. Does setting BATCH in the environment not work? Unfortunately not. I tried: $ BATCH=yes portmaster -a -d --no-confirm and like someone else suggested adding BATCH?=yes to /etc/make.conf, then running: $ portmaster -a -d --no-confirm Still asks me to confirm all the options. Sandra ___ 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: i keep *trying* to move from portupgrade to portmaster
On Fri, Aug 6, 2010 at 3:38 PM, Freddie Cash fjwc...@gmail.com wrote: On Fri, Aug 6, 2010 at 6:26 AM, Sandra Kachelmann s.kachelm...@googlemail.com wrote: On Fri, Aug 6, 2010 at 2:44 PM, Sandra Kachelmann s.kachelm...@googlemail.com wrote: On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer schweizer.mar...@gmail.com wrote: Hello Sandra I was in a similar situation. I found the following paramters very usefull: portmaster -a -d --no-confirm -a: Take all installed ports -d: Delete any dependicies -no--confirm: Wait not after the check which ports are upgradable and like someone else suggested adding BATCH?=yes to /etc/make.conf, then running: $ portmaster -a -d --no-confirm Still asks me to confirm all the options. If you absolutely do not want to see the OPTIONS screens, no matter what, then add -G (see man page for details). I tried that but if i run $ portmaster --no-confirm -G /usr/ports/x11/xorg The libiconv OPTIONS dialog pops up. Sandra ___ 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: i keep *trying* to move from portupgrade to portmaster
On Fri, Aug 6, 2010 at 3:59 PM, Sandra Kachelmann s.kachelm...@googlemail.com wrote: On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More amvandem...@gmail.com wrote: On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash fjwc...@gmail.com wrote: If you absolutely do not want to see the OPTIONS screens, no matter what, then add -G (see man page for details). No, that's not what -G does. -G makes portmaster handle the options screen similar to portupgrade eg waiting to ask you until it runs into it. Setting BATCH=yes in make.conf does work, maybe BATCH?=yes breaks it, my make.conf fu is only sightly better than it documentation which isn't much. -- Adam Vande More OK, that does work: Setting BATCH=yes in /etc/make.conf and running: $ portmaster --no-confirm -G /usr/ports/x11/xorg But is there really no way to specify it as argument of portmaster? Sandra Think I found it: portmaster --no-confirm -G -m 'BATCH=yes' /usr/ports/x11/xorg This seems to do what I want. Still --batch would be nice - guess I'll create a shell alias. Sorry for all the lame questions - it seems that I want something really special nobody else is interested in. Sandra ___ 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: i keep *trying* to move from portupgrade to portmaster
On Fri, Aug 6, 2010 at 4:09 PM, Sandra Kachelmann s.kachelm...@googlemail.com wrote: On Fri, Aug 6, 2010 at 3:59 PM, Sandra Kachelmann s.kachelm...@googlemail.com wrote: On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More amvandem...@gmail.com wrote: On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash fjwc...@gmail.com wrote: If you absolutely do not want to see the OPTIONS screens, no matter what, then add -G (see man page for details). No, that's not what -G does. -G makes portmaster handle the options screen similar to portupgrade eg waiting to ask you until it runs into it. Setting BATCH=yes in make.conf does work, maybe BATCH?=yes breaks it, my make.conf fu is only sightly better than it documentation which isn't much. -- Adam Vande More OK, that does work: Setting BATCH=yes in /etc/make.conf and running: $ portmaster --no-confirm -G /usr/ports/x11/xorg But is there really no way to specify it as argument of portmaster? Sandra Think I found it: portmaster --no-confirm -G -m 'BATCH=yes' /usr/ports/x11/xorg This seems to do what I want. Still --batch would be nice - guess I'll create a shell alias. Sorry for all the lame questions - it seems that I want something really special nobody else is interested in. Hmm... I just tried to update an outdated system with: $ portmaster --no-confirm -G -m 'BATCH=yes' -a after a while it asked me whether I want to delete pcre - so -m BATCH=yes does not work. Sandra ___ 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: i keep *trying* to move from portupgrade to portmaster
On Fri, Aug 6, 2010 at 4:31 PM, Freddie Cash fjwc...@gmail.com wrote: On Fri, Aug 6, 2010 at 7:28 AM, Sandra Kachelmann s.kachelm...@googlemail.com wrote: I just tried to update an outdated system with: $ portmaster --no-confirm -G -m 'BATCH=yes' -a after a while it asked me whether I want to delete pcre - so -m BATCH=yes does not work. What's the exact message? Is it asking about deleting old distfiles? There's an option to always delete (don't ask) and another option to always ask. It's -d (just delete the distfile, don't ask) and -D (always ask before deleting a distfile). If not, what's the question being asked? Here is another one: ... test -z /usr/local/share/common-lisp/source/gpg-error || ../.././install-sh -c -d /usr/local/share/common-lisp/source/gpg-error install -o root -g wheel -m 444 'gpg-error-codes.lisp' '/usr/local/share/common-lisp/source/gpg-error/gpg-error-codes.lisp' cd /usr/ports/security/libgpg-error/work/libgpg-error-1.8 install -o root -g wheel -m 444 AUTHORS ChangeLog NEWS README /usr/local/share/doc/libgpg-error === Running ldconfig /sbin/ldconfig -m /usr/local/lib === Registering installation for libgpg-error-1.8 === Cleaning for libgpg-error-1.8 === Updating dependency entry for libgpg-error-1.8 in each dependent port === Upgrade of libgpg-error-1.7_1 to libgpg-error-1.8 succeeded === Delete libgpg-error-1.7.tar.bz2? y/n [n] Sandra ___ 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: i keep *trying* to move from portupgrade to portmaster
On Fri, Aug 6, 2010 at 4:30 PM, Adam Vande More amvandem...@gmail.com wrote: On Fri, Aug 6, 2010 at 9:28 AM, Sandra Kachelmann s.kachelm...@googlemail.com wrote: Hmm... I just tried to update an outdated system with: $ portmaster --no-confirm -G -m 'BATCH=yes' -a after a while it asked me whether I want to delete pcre - so -m BATCH=yes does not work. Come on, please read the man page. Ignore me if you don't want to help. The man page is too huge. Sandra ___ 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: xfce4/xorg problem amd64
On Wed, May 19, 2010 at 6:13 PM, Gary Jennejohn gljennj...@googlemail.com wrote: On Wed, 19 May 2010 15:56:05 +0200 Sandra Kachelmann s.kachelm...@googlemail.com wrote: Since the xorg update my xfce4 desktop has become unusable. I always get the error message below. I even setup FreeBSD 8.0-RELEASE from scratch, updated to 8.0-STABLE, installed xorg and xfce4 with default settings: $ portinstall --batch /usr/ports/x11/xorg /usr/ports/x11-wm/xfce4 portinstall? What's that? portinstall is part of ports-mgmt/portupgrade THE ports management tool way back in time when portmaster wasn't around :-) You could try adding --enable-checks=no to CONFIGURE_ARGS in /usr/ports/devel/dbus/Makefile and reinstalling dbus. This option disables all the safety checks which are being triggered. Might help. Thanks, I tried that. Unfortunately it didn't help. I wonder if the upcomming xfce 4.6.2 release is going to fix this. Sandra ___ 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: xfce4/xorg problem amd64
On Thu, May 20, 2010 at 8:55 AM, S Roberts sta...@vickiandstacey.com wrote: Hello, On Thu, 20 May 2010 08:51:07 +0200 Sandra Kachelmann s.kachelm...@googlemail.com wrote: On Wed, May 19, 2010 at 6:13 PM, Gary Jennejohn gljennj...@googlemail.com wrote: On Wed, 19 May 2010 15:56:05 +0200 Sandra Kachelmann s.kachelm...@googlemail.com wrote: Since the xorg update my xfce4 desktop has become unusable. I always get the error message below. I even setup FreeBSD 8.0-RELEASE from scratch, updated to 8.0-STABLE, installed xorg and xfce4 with default settings: $ portinstall --batch /usr/ports/x11/xorg /usr/ports/x11-wm/xfce4 portinstall? What's that? portinstall is part of ports-mgmt/portupgrade THE ports management tool way back in time when portmaster wasn't around :-) You could try adding --enable-checks=no to CONFIGURE_ARGS in /usr/ports/devel/dbus/Makefile and reinstalling dbus. This option disables all the safety checks which are being triggered. Might help. Thanks, I tried that. Unfortunately it didn't help. I wonder if the upcomming xfce 4.6.2 release is going to fix this. I was thinking of trying XFCE on FreeBSD-8-Stable, but this problem has me concerned. Has anyone actually bugged this as yet, though? I imagine its not very likely to get addressed (at least officially) unless there's a PR to work against., PR: 146295 - it probably doesn't get fixed until 4.6.2: http://old.nabble.com/upcomming-xfce-4.6.2-release-td28584690.html Sandra ___ 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
xfce4/xorg problem amd64
Hi Since the xorg update my xfce4 desktop has become unusable. I always get the error message below. I even setup FreeBSD 8.0-RELEASE from scratch, updated to 8.0-STABLE, installed xorg and xfce4 with default settings: $ portinstall --batch /usr/ports/x11/xorg /usr/ports/x11-wm/xfce4 Then I moved my homedir away to avoid any cruft in .config or wherever. Setup .ininitrc .session $ cat .xinitrc if [ -f ~/.xsession ]; then . ~/.xsession fi $ cat .xsession cd xset b off /usr/local/bin/numlockx exec sh /usr/local/etc/xdg/xfce4/xinitrc So now everything should be completely vanilla: skachelm...@valhalla:~ $ startx xauth: creating new authority file /home/skachelmann/.serverauth.7426 X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.0-STABLE amd64 Current Operating System: FreeBSD valhalla.local 8.0-STABLE FreeBSD 8.0-STABLE #0: Fri May 7 20:43:11 CEST 2010 r...@valhalla.local:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 19 May 2010 12:50:03AM Current version of pixman: 0.16.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed May 19 15:41:10 2010 (==) Using config file: /etc/X11/xorg.conf record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 stdin:1:3: error: invalid preprocessing directive #Those stdin:2:3: error: invalid preprocessing directive #or stdin:3:3: error: invalid preprocessing directive #Xft stdin:4:3: error: invalid preprocessing directive #Xft xrdb: Xft.hinting on line 9 overrides entry on line 6 xrdb: Xft.hintstyle on line 11 overrides entry on line 7 xfdesktop[7480]: starting up process 7466: arguments to dbus_message_new_signal() were incorrect, assertion _dbus_check_is_valid_path (path) failed in file dbus-message.c line 1165. This is normally a bug in some application using the D-Bus library. D-Bus not compiled with backtrace support so unable to print a backtrace Abort trap (core dumped) (xfce4-settings-helper:7482): libxfcegui4-WARNING **: ICE I/O Error waiting for X server to shut down (xfce4-settings-helper:7485): xfce4-settings-helper-WARNING **: Failed to connect to session manager xfce4-settings-helper: Fatal IO error 53 (Software caused connection abort) on X server :0.0. xfwm4: Fatal IO error 2 (No such file or directory) on X server :0.0. xfce4-panel: Fatal IO error 0 (Unknown error: 0) on X server :0.0. dbus and hal are running. Any help to solve this nightmare is gratefully appreciated! Sandra ___ 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
installing java
Today I had the pleasure to install some java port and well it was quite frustrating. I still have to download all the distfiles manually. Isn't FreeBSD now officially supported by Sun? Is it really still necessary to manually fetch the distfiles or is this something that could be looked at again? Theoretically: What if the port would just point to the distfiles and don't actually host them on any FreeBSD mirror. Wouldn't that be legal? I mean a link some site that provides instruction on how to build an atomic bomb is still legal as well, right? If so I could simply upload the distfiles to some russian FTP server and nobody but Sun would really care. This is so annyoing: - Manually fetch - Login to some bloated sun.com site ARGHH!!! /frustration Sandra ___ 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: .Xdefaults ignored
On Thu, Dec 17, 2009 at 5:53 PM, Chris Rees utis...@googlemail.com wrote: 2009/12/17 Sandra Kachelmann s.kachelm...@googlemail.com: I recently noticed that xorg under FreeBSD ignores my ~/.Xdefaults file. I saw with truss that instead .Xdefaults-fqdn is being used: open(/home/skmn/.Xdefaults-prissy.local,O_RDONLY,06362252327) = 5 (0x5) No trace about ~/.Xdefaults Any idea why and if it can be changed? Sandra Does .Xdefaults-fqdn exist? If so, it read that instead, and that is the sensible behaviour; the name is more specific. Try renaming or deleting .Xdefaults-fqdn and see if it helps. Sorry, I should have mentioned before. As a consequence of xorg ignoring my .Xdefaults I've created .Xdefaults-fqdn and it's being used. That's not the problem. I'd like to change that behaviour though because pretty much all other Linux distros I've ever used before used .Xdefaults and most documentation you find about .Xdefaults entries point user to .Xdefaults in the homedir. Yeah I could create symlinks but I rather change it completely to .Xdefaults. I deploy a tarball with all my dotfiles on a Webserver and I don't want to rename .Xdefaults on every workstation I fetch the tarballs via script. I bet the search path of .Xdefaults is some sort of config option that can be changed somewhere. I tried searching in /usr/local/lib/X11, env startx, env xorg but no luck. Any idea where I can change it? Sandra ___ 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
.Xdefaults ignored
I recently noticed that xorg under FreeBSD ignores my ~/.Xdefaults file. I saw with truss that instead .Xdefaults-fqdn is being used: open(/home/skmn/.Xdefaults-prissy.local,O_RDONLY,06362252327) = 5 (0x5) No trace about ~/.Xdefaults Any idea why and if it can be changed? Sandra ___ 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
mail/perdition 1.18 available
Hi Version 1.18 of perdition is available. Could you please update the port? Sandra ___ 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: squeezecenter 7.3.2 no longer starts with latest ports
Hi, I just tried to restart /usr/ports/audio/squeezecenter version 7.3.2 following a reboot and I'm now receiving this error: sudo /usr/local/etc/rc.d/squeezecenter start Starting squeezecenter. Found custom OS support file for unix The following CPAN modules were found but cannot work with SqueezeCenter: Net::DNS (loaded 0.63, need 0.63) To fix this problem you have several options: 1. Install the latest version of the module(s) using CPAN: sudo cpan Some::Module 2. Update the module's package using apt-get, yum, etc. 3. Run the .tar.gz version of SqueezeCenter which includes all required CPAN modules. I guess I've updated a few perl related ports in the last couple of days since I last rebooted, one of which I presume has cause squeezecenter to fail. My installed ports are current as of last night. If relevant, my system is running 6.4-RELEASE-p1. Backing p5-Net-DNS down to 0.64 (from 0.65), has not helped but I'm not even sure this port uses the ports installed version anyway! All ideas welcome please!! It doesn't work for me either: # /usr/local/etc/rc.d/squeezeboxserver start Starting squeezeboxserver. Can't use string (0) as a HASH ref while strict refs in use at /usr/local/lib/perl5/site_perl/5.8.9/mach/Class/XSAccessor/Array.pm line 61. Compilation failed in require at (eval 182) line 3. ...propagated at /usr/local/lib/perl5/5.8.9/base.pm line 93. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Networking/Async/HTTP.pm line 36. Compilation failed in require at /usr/local/squeezeboxserver/Slim/Networking/SimpleAsyncHTTP.pm line 27. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Networking/SimpleAsyncHTTP.pm line 27. Compilation failed in require at /usr/local/squeezeboxserver/Slim/Schema.pm line 43. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Schema.pm line 43. Compilation failed in require at /usr/local/squeezeboxserver/Slim/Player/Song.pm line 19. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Player/Song.pm line 19. Compilation failed in require at /usr/local/squeezeboxserver/Slim/Player/StreamingController.pm line 18. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Player/StreamingController.pm line 18. Compilation failed in require at /usr/local/squeezeboxserver/Slim/Player/Client.pm line 29. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Player/Client.pm line 29. Compilation failed in require at /usr/local/squeezeboxserver/Slim/Utils/Alarm.pm line 48. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Utils/Alarm.pm line 48. Compilation failed in require at /usr/local/squeezeboxserver/Slim/Buttons/Alarm.pm line 12. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Buttons/Alarm.pm line 12. Compilation failed in require at /usr/local/squeezeboxserver/Slim/Buttons/Common.pm line 42. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/Slim/Buttons/Common.pm line 42. Compilation failed in require at /usr/local/squeezeboxserver/slimserver.pl line 163. BEGIN failed--compilation aborted at /usr/local/squeezeboxserver/slimserver.pl line 163. I even removed the whole database and performed a complete rebuild: $ portupgrade -rf squeezeboxserver This port is broken... Sandra ___ 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: remove BUILD_DEPENDS automatically after install
(portmaster author cc:ed) On Mon, Nov 16, 2009 at 1:06 AM, Erik Trulsson ertr1...@student.uu.se wrote: On Sun, Nov 15, 2009 at 11:44:04PM +0100, Sandra Kachelmann wrote: Is there a reason why BUILD_DEPENDS aren't being removed after a port has been installed and if no other installed port depends on it? How do you know that the user does not want that port installed? And what if the user will install 20 other ports afterwards - all of which is that same port as a BUILD_DEPENDS - should that port be installed/deinstalled each and every time? It would be nice if this was configurable. Maybe it could be even integrated into portupgrade or portmaster. If such a port is installed directly it could get a package entry DIRECT_INSTALLED=yes in /var/db/pkg/.. or something (there is probably a better way to do this). (Personally I would be *very* annoyed if, for example, libtool or automake/autoconf would be reinstalled every time I installed a port which had one of them as a build-time dependency. There are *lots* of ports which have one of them in BUILD_DEPENDS, but few if any that has them as RUN_DEPENDS.) Even nicer if execptions would be configurable. There are loads of ports that install BUILD_DEPENDS that are never used again. cvsup for instance pulls in a gigantic tree of esoteric ports I can't even pronounce. Sure I could install the package, take cvsup-without-gui or even use portsnap but this is not the point here. Sandra ___ 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: remove BUILD_DEPENDS automatically after install
On Tue, Nov 17, 2009 at 12:58 AM, Doug Barton do...@freebsd.org wrote: Sandra Kachelmann wrote: (portmaster author cc:ed) On Mon, Nov 16, 2009 at 1:06 AM, Erik Trulsson ertr1...@student.uu.se wrote: On Sun, Nov 15, 2009 at 11:44:04PM +0100, Sandra Kachelmann wrote: Is there a reason why BUILD_DEPENDS aren't being removed after a port has been installed and if no other installed port depends on it? How do you know that the user does not want that port installed? And what if the user will install 20 other ports afterwards - all of which is that same port as a BUILD_DEPENDS - should that port be installed/deinstalled each and every time? It would be nice if this was configurable. Maybe it could be even integrated into portupgrade or portmaster. If such a port is installed directly it could get a package entry DIRECT_INSTALLED=yes in /var/db/pkg/.. or something (there is probably a better way to do this). I have a new feature in the svn version of portmaster called --packages-build that for any given run creates an internal list of dependencies that are only ever listed as build deps (never run deps) and installs packages for them but builds everything else. This feature was created at the request of one of companies that sponsored the package installation code. Currently it does not pkg_delete those packages when it's done, but I could easily add that. This is exactly what I was looking for. Actually I suppose it would not be too hard to extend that list of build only deps idea to a general feature which deletes them when done. Something like --delete-build-only maybe? This would be limited I would find such an option extremely useful. to the subset of the list of build-only deps that portmaster actually installed. Just because something is build-only for a given run of portmaster doesn't mean that it isn't a run dep for something else if it is already installed. Or if it's already installed before the actual port build it could be considered as wanted and therefor not to be deleted after the build. Just out of curiosity, is your svn repository publicly accessible? Thank you so much for the good work. Sandra ___ 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
remove BUILD_DEPENDS automatically after install
Is there a reason why BUILD_DEPENDS aren't being removed after a port has been installed and if no other installed port depends on it? Sandra ___ 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: libmapi new port request
Could someone please make a port for libmapi? http://www.openchange.org http://downloads.sourceforge.net/openchange/libmapi-0.8.2-ROMULUS.tar.gz Sandra I got it almost ready for commit :) Just wait a little bit while I find time to clean it up. You're still working on it? Sandra ___ 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
libmapi new port request
Could someone please make a port for libmapi? http://www.openchange.org http://downloads.sourceforge.net/openchange/libmapi-0.8.2-ROMULUS.tar.gz Sandra ___ 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
new port: p5-Inline::C (request)
Could someone(tm) please add a port for: http://search.cpan.org/~sisyphus/Inline-0.45/C/C.pod Thanks in advance. Sandra ___ 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: portupgrade-devel: portversion -vl'' does not show current version
Hi I _really_ still miss this functionality :-( Could you please re-implement it? Sandra Sergey Matveychuk s...@freebsd.org Date 3 Jul 2008 09:50:58 Subject Re: portupgrade-devel: portversion -vl'' does not show current version Message-ID 486ca0af.3020...@freebsd.org In reply to Sandra Kachelmann References to Sandra Kachelmann Replies Robert Huff Referenced by Robert Huff, Sergey Matveychuk Sandra Kachelmann wrote: After upgrading from portupgrade to portupgrade-devel the command $ portversion -vl'' does not show the _current_ version anymore. Why was it removed? I found the information useful. before: gnutls-2.4.0 needs updating (port has 2.4.1) now: gnutlsneeds updating (port has 2.4.1) Looks like it's a side effect of new options implementation. Now you can use -Fvl options. But I'll think to back this functionality. Thanks. -- Dixi. Sem. ___ 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
ansi colors in ports
Why does freebsd ports not use ansi colors? This would be so nice :-) Eg. ECHO_MSG would be so much more visible within the compilation soup. Gentoo uses colors too! Sandra ___ 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
www/nspluginwrapper is outdated
Hi www/nspluginwrapper is outdated. Version 1.1.2 is available. Could you please update it? A later version than 1.0.0 is requred with flash10 (at least under linux). Thanks. Sandra ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
games/warsow and games/warsow-data ouf of date
Hi games/warsow and games/warsow-data are out of date and the mouse isn't working with the version in ports, however there is 0.42 available. Do you have any plans on updating the port? Sandra ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade-devel: portversion -vl'' does not show current version
After upgrading from portupgrade to portupgrade-devel the command $ portversion -vl'' does not show the _current_ version anymore. Why was it removed? I found the information useful. before: gnutls-2.4.0 needs updating (port has 2.4.1) now: gnutlsneeds updating (port has 2.4.1) S. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
