Re: Package location
On Mar 2, 2008, at 23:50, Scot Hetzel wrote: On 3/2/08, Doug Hardie [EMAIL PROTECTED] wrote: Adding ports to FreeBSD 7 I normally build from source and create a package. With previous versions the created packages went into /usr/ ports/packages/All. However the packages directory was not created on a new installation. The packages were being built in the ports top level directory. Before I noticed that, I created a packages directory and the remaining packages are being built in it as before. I didn't find any indications of a change in the various notes with the release. Has there been a change in the package structure? That is how it always worked. If you don't create the /usr/ports/packages directory, then make package in /usr/ports/category/port will place the newly created package in this directory. I don't recall ever having to create the directory. Seems like the base install created it for me. Anyway, I have moved all of them there and everything seems to work fine. Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
interactive ports - the plague
I don't mind ports that use the config framework. You can deal with them without trouble by setting BATCH, using portmaster or portconfig-recursive from bsdadminscripts. But I find ports like ghostscript-gpl that open an ncurses dialogue between configure and build stage very annoying. They are the reason one wakes up in the morning and finds out that instead of having finished all updates, the machine hasn't even started updating, because it's just hanging there, waiting with a config dialogue that doesn't even remember what I choose last time. I cannot find any policy on interactive ports in the Porters' Handbook. Maybe there aught to be one. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Current unassigned ports problem reports
Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems Serious problems S Tracker Resp. Description o ports/106369vpnd caused kernel panic with ppp mode o ports/106372vpnd can't run with slip mode f ports/108077www/linux-flashplugin9 crashes linux-firefox o ports/108413[patch] net/vnc does not works. o ports/111430[ PATCH ] security/isakmpd with OpenSSL 0.9.8b and new f ports/112921x11-wm/Beryl not loading focus and keybinding settings s ports/113144print/ghostscript-gnu dumps core with several output d f ports/115818Executable clash between databases/grass and ruby gems o ports/116378xorg 7.3 on -stable breaks math/scilab f ports/116385net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/116586net/isc-dhcp3-server does not work when compiled with f ports/116777The math/scilab port fails in demos-signal-bode. f ports/116778security/nmap ping-scan misses some hosts o ports/117025multimedia/pwcbsd: Pwcbsd-1.4.0 + New USBStack not wor o ports/117128security/ipsec-tools racoon.sh fails with /var on mfs o ports/117196Port net/asterisk-addons 1.4.2 fails to compile o ports/118877audio/streamripper does not detect song title from str f ports/119546net/nss_ldap makes /usr/bin/ssh dump core in getpwuid( o ports/120372java/linux-sun-jdk16: linux-sun-jre1.6.0 plugin doesn' o ports/120505[maintainer] net/phpldapadmin, net/phpldapadmin098 -- o ports/120837New port: astro/gpscorrelate; Corelate exif metadata o o ports/120866Update devel/py-setuptools 0.6c7_1 - 0.6c8 f ports/120996x11-toolkits/swt-devel: gnomevfs depenency problem f ports/121095change download location for sysutils/mountsmb2 o ports/121179emulators/hfsutils - emulators/hfs - 2 ports install f o ports/121247[patch] x11/xcolors built from port fails to find rgb. 26 problems total. Non-critical problems S Tracker Resp. Description o ports/102544ltmdm driver (comms/ltmdm) crashes system whene line r o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM f ports/107937jailed net/isc-dhcp3-server wouldn't run with an immut o ports/110144New port: math/Matlab7 o ports/110697New port: ports-mgmt/pkg_deps o ports/111456[UPDATE] finance/pfpro updated distinfo s ports/112887net/nxserver 1.4.0_1 fails to compile after upgrading o ports/113423Update for ports net/freenx to version 0.6.0 f ports/114127net/vnc - vnc.so installed to bad location o ports/114825pam module security/pam_abl not working s ports/115216ADA devel/florist exit_process program doesn't compile s ports/115217Ada devel/florist socket program doesn't compile due t f ports/115304multimedia/gpac-mp4box cannot import files larger than o ports/115308multimedia/jahshaka fails to open GUI - ends with pre f ports/115336port multimedia/avifile on FreeBSD 7.0 not BROKEN with f ports/115627www/Lynx (-ssl) does not correctly test for OpenSSL f ports/115722New port:x11/tastymenu A K-Menu replacement for KDE 3. o ports/116037multimedia/dvd-slideshow has been updated from 0.7.5 t f ports/116058Update: x11-themes/gtk-qt-engine to version 0.8 f
Re: interactive ports - the plague
On Mon, 03 Mar 2008 10:24:21 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: I don't mind ports that use the config framework. You can deal with them without trouble by setting BATCH, using portmaster or portconfig-recursive from bsdadminscripts. But I find ports like ghostscript-gpl that open an ncurses dialogue between configure and build stage very annoying. They are the reason one wakes up in the morning and finds out that instead of having finished all updates, the machine hasn't even started updating, because it's just hanging there, waiting with a config dialogue that doesn't even remember what I choose last time. I cannot find any policy on interactive ports in the Porters' Handbook. Maybe there aught to be one. Setting BATCH is supposed to prevent genuinely interactive ports from building (that's actually the original purpose of BATCH). In my experience ghostscript-gpl will build with default options if you set BATCH, or are you saying that you need a specific non-default option? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
RW wrote: On Mon, 03 Mar 2008 10:24:21 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: I don't mind ports that use the config framework. You can deal with them without trouble by setting BATCH, using portmaster or portconfig-recursive from bsdadminscripts. But I find ports like ghostscript-gpl that open an ncurses dialogue between configure and build stage very annoying. They are the reason one wakes up in the morning and finds out that instead of having finished all updates, the machine hasn't even started updating, because it's just hanging there, waiting with a config dialogue that doesn't even remember what I choose last time. I cannot find any policy on interactive ports in the Porters' Handbook. Maybe there aught to be one. Setting BATCH is supposed to prevent genuinely interactive ports from building (that's actually the original purpose of BATCH). In my experience ghostscript-gpl will build with default options if you set BATCH, or are you saying that you need a specific non-default option? I believe a good example of what he might be talking about is the jdk ports. Because of the licensing of those ports, they will bring up an EULA that you need to read and then type yes afterwards. Even with BATCH set, it still stops at that EULA. Naram Qashat ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
polypaudio
Hi Hi I have been out of commission for some time due to some health problems. When to ujpgrade and received the forllowing error message can anyone please advise? Thanks david # portupgrade -a Stale dependency: amavisd-new-2.5.3,1 -- p5-DBD-mysql-4.006 -- manually run 'pkgdb -F' to fix, or specify -O to force. [EMAIL PROTECTED] /usr1/samba/sambap/feb/2359_2575_P]# pkgdb -F --- Checking the package registry database Stale origin: 'audio/akode-plugins-polypaudio': perhaps moved or obsoleted. - The port 'audio/akode-plugins-polypaudio' was removed on 2008-01-01 because: Polypaudio is obsolete in favor of pulseaudio - Hint: akode-plugins-polypaudio-2.0.1_1,1 is required by the following package(s): kdemultimedia-3.5.8 kde-3.5.8 akode-2.0.1,1 - Hint: checking for overwritten files... - No files installed by akode-plugins-polypaudio-2.0.1_1,1 have been overwritten by other packages. Deinstall akode-plugins-polypaudio-2.0.1_1,1 ? [no] y --- Deinstalling 'akode-plugins-polypaudio-2.0.1_1,1' pkg_delete: package 'akode-plugins-polypaudio-2.0.1_1,1' is required by these other packages and may not be deinstalled: akode-2.0.1,1 kde-3.5.8 kdemultimedia-3.5.8 ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! akode-plugins-polypaudio-2.0.1_1,1(pkg_delete failed) Command failed [exit code 1]: /usr/local/sbin/pkg_deinstall akode-plugins-polypaudio-2.0.1_1,1 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mon, 03 Mar 2008 11:27:31 -0500 Naram Qashat [EMAIL PROTECTED] wrote: RW wrote: On Mon, 03 Mar 2008 10:24:21 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: I don't mind ports that use the config framework. You can deal with them without trouble by setting BATCH, using portmaster or portconfig-recursive from bsdadminscripts. But I find ports like ghostscript-gpl that open an ncurses dialogue between configure and build stage very annoying. Setting BATCH is supposed to prevent genuinely interactive ports from building (that's actually the original purpose of BATCH). I believe a good example of what he might be talking about is the jdk ports. Because of the licensing of those ports, they will bring up an EULA that you need to read and then type yes afterwards. Even with BATCH set, it still stops at that EULA. IIRC these ports refuse to fetch the distfiles, and ask you to fetch them manually from the websites, where you have to agree to the terms, they aren't actually interactive. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mon, Mar 03, 2008 at 05:04:57PM +, RW wrote: On Mon, 03 Mar 2008 11:27:31 -0500 Naram Qashat [EMAIL PROTECTED] wrote: RW wrote: On Mon, 03 Mar 2008 10:24:21 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: I don't mind ports that use the config framework. You can deal with them without trouble by setting BATCH, using portmaster or portconfig-recursive from bsdadminscripts. But I find ports like ghostscript-gpl that open an ncurses dialogue between configure and build stage very annoying. Setting BATCH is supposed to prevent genuinely interactive ports from building (that's actually the original purpose of BATCH). I believe a good example of what he might be talking about is the jdk ports. Because of the licensing of those ports, they will bring up an EULA that you need to read and then type yes afterwards. Even with BATCH set, it still stops at that EULA. IIRC these ports refuse to fetch the distfiles, and ask you to fetch them manually from the websites, where you have to agree to the terms, they aren't actually interactive. While true there are at least two ports which are interactive beyond OPTIONS and license things. I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. security/tripwire asks some setup questions during the post-install. I don't recall how BATCH affects these two ports, if at all. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
Naram Qashat wrote: I believe a good example of what he might be talking about is the jdk ports. Because of the licensing of those ports, they will bring up an EULA that you need to read and then type yes afterwards. Even with BATCH set, it still stops at that EULA. With me the JDK ports stop and demand I manually download the files, which is even more irritating -- View this message in context: http://www.nabble.com/interactive-ports---the-plague-tp15800371p15808613.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 [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mon, 3 Mar 2008 12:27:50 -0500 Wesley Shields [EMAIL PROTECTED] wrote: On Mon, Mar 03, 2008 at 05:04:57PM +, RW wrote: IIRC these ports refuse to fetch the distfiles, and ask you to fetch them manually from the websites, where you have to agree to the terms, they aren't actually interactive. While true there are at least two ports which are interactive beyond OPTIONS and license things. I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. security/tripwire asks some setup questions during the post-install. I don't recall how BATCH affects these two ports, if at all. tripwire is marked as interactive, so it wont build. I'm not sure about postfix. does it prompt on upgrades too? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
RW wrote: On Mon, 03 Mar 2008 10:24:21 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: I don't mind ports that use the config framework. You can deal with them without trouble by setting BATCH, using portmaster or portconfig-recursive from bsdadminscripts. But I find ports like ghostscript-gpl that open an ncurses dialogue between configure and build stage very annoying. They are the reason one wakes up in the morning and finds out that instead of having finished all updates, the machine hasn't even started updating, because it's just hanging there, waiting with a config dialogue that doesn't even remember what I choose last time. I cannot find any policy on interactive ports in the Porters' Handbook. Maybe there aught to be one. Setting BATCH is supposed to prevent genuinely interactive ports from building (that's actually the original purpose of BATCH). But this will also keep the config screens away from me, which can be handled before all builds quite comfortably. In my experience ghostscript-gpl will build with default options if you set BATCH, or are you saying that you need a specific non-default option? I'd prefer the port to use the ports config framework. In that case I'd even bother to go through the list of drivers and make choices. At the moment I just select OK, because what I choose won't be remembered the next time anyway. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mon, Mar 03, 2008 at 06:36:57PM +, RW wrote: On Mon, 3 Mar 2008 12:27:50 -0500 Wesley Shields [EMAIL PROTECTED] wrote: On Mon, Mar 03, 2008 at 05:04:57PM +, RW wrote: IIRC these ports refuse to fetch the distfiles, and ask you to fetch them manually from the websites, where you have to agree to the terms, they aren't actually interactive. While true there are at least two ports which are interactive beyond OPTIONS and license things. I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. security/tripwire asks some setup questions during the post-install. I don't recall how BATCH affects these two ports, if at all. tripwire is marked as interactive, so it wont build. I'm not sure about postfix. does it prompt on upgrades too? Yes. Have a look at pkg-install. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mon, Mar 03, 2008 at 09:12:37AM -0800, pjd wrote: With me the JDK ports stop and demand I manually download the files, which is even more irritating Given Sun's licensing requirements, what is your suggestion? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mar 3, 2008, at 12:27 PM, Wesley Shields wrote: I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. I'll take that as a bug report :-) Though I'm not sure which way it should default, on BATCH. And does BATCH apply to package install as well? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package location
On Mon, 3 Mar 2008 00:39:54 -0800 Doug Hardie [EMAIL PROTECTED] wrote: On Mar 2, 2008, at 23:50, Scot Hetzel wrote: On 3/2/08, Doug Hardie [EMAIL PROTECTED] wrote: Adding ports to FreeBSD 7 I normally build from source and create a package. With previous versions the created packages went into /usr/ ports/packages/All. However the packages directory was not created on a new installation. The packages were being built in the ports top level directory. Before I noticed that, I created a packages directory and the remaining packages are being built in it as before. I didn't find any indications of a change in the various notes with the release. Has there been a change in the package structure? That is how it always worked. If you don't create the /usr/ports/packages directory, then make package in /usr/ports/category/port will place the newly created package in this directory. I don't recall ever having to create the directory. Seems like the base install created it for me. Anyway, I have moved all of them there and everything seems to work fine. Thanks. Probably you chose not to install the ports tarball. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect signature.asc Description: PGP signature
Re: Package location
On Mar 3, 2008, at 11:43, Ion-Mihai Tetcu wrote: On Mon, 3 Mar 2008 00:39:54 -0800 Doug Hardie [EMAIL PROTECTED] wrote: On Mar 2, 2008, at 23:50, Scot Hetzel wrote: On 3/2/08, Doug Hardie [EMAIL PROTECTED] wrote: Adding ports to FreeBSD 7 I normally build from source and create a package. With previous versions the created packages went into /usr/ ports/packages/All. However the packages directory was not created on a new installation. The packages were being built in the ports top level directory. Before I noticed that, I created a packages directory and the remaining packages are being built in it as before. I didn't find any indications of a change in the various notes with the release. Has there been a change in the package structure? That is how it always worked. If you don't create the /usr/ports/packages directory, then make package in /usr/ports/category/port will place the newly created package in this directory. I don't recall ever having to create the directory. Seems like the base install created it for me. Anyway, I have moved all of them there and everything seems to work fine. Thanks. Probably you chose not to install the ports tarball. Nope. That was selected and installed. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mon, Mar 03, 2008 at 03:01:00PM -0500, Vivek Khera wrote: On Mar 3, 2008, at 12:27 PM, Wesley Shields wrote: I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. I'll take that as a bug report :-) I didn't intend for that to be a bug report. :) Though I'm not sure which way it should default, on BATCH. And does BATCH apply to package install as well? Honestly, I have not put much thought into it. I was just pointing out that some ports require post-installation questions to be answered. Thanks for your work on postfix, it's always just worked for me. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
Wesley Shields wrote: On Mon, Mar 03, 2008 at 05:04:57PM +, RW wrote: On Mon, 03 Mar 2008 11:27:31 -0500 Naram Qashat [EMAIL PROTECTED] wrote: RW wrote: On Mon, 03 Mar 2008 10:24:21 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: I don't mind ports that use the config framework. You can deal with them without trouble by setting BATCH, using portmaster or portconfig-recursive from bsdadminscripts. But I find ports like ghostscript-gpl that open an ncurses dialogue between configure and build stage very annoying. Setting BATCH is supposed to prevent genuinely interactive ports from building (that's actually the original purpose of BATCH). I believe a good example of what he might be talking about is the jdk ports. Because of the licensing of those ports, they will bring up an EULA that you need to read and then type yes afterwards. Even with BATCH set, it still stops at that EULA. IIRC these ports refuse to fetch the distfiles, and ask you to fetch them manually from the websites, where you have to agree to the terms, they aren't actually interactive. While true there are at least two ports which are interactive beyond OPTIONS and license things. I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. security/tripwire asks some setup questions during the post-install. I don't recall how BATCH affects these two ports, if at all. Another case is print/xdvi: it asks for a font directory. Unless you specify one it hangs there forever waiting for input. However, it didn't bother me enough yet to fix this... ;-) Regards, Philipp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
Vivek Khera wrote: On Mar 3, 2008, at 12:27 PM, Wesley Shields wrote: I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. I'll take that as a bug report :-) Though I'm not sure which way it should default, on BATCH. And does BATCH apply to package install as well? I think the usual way is to mention in pkg-message what aught to be done instead of offering to do it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Monday 03 March 2008, Mark Linimon said: On Mon, Mar 03, 2008 at 09:12:37AM -0800, pjd wrote: With me the JDK ports stop and demand I manually download the files, which is even more irritating Given Sun's licensing requirements, what is your suggestion? -- --- Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Monday 03 March 2008, Beech Rintoul said: On Monday 03 March 2008, Mark Linimon said: On Mon, Mar 03, 2008 at 09:12:37AM -0800, pjd wrote: With me the JDK ports stop and demand I manually download the files, which is even more irritating Given Sun's licensing requirements, what is your suggestion? Sorry, having that port just fail seems to be the right thing to do. FWIW, it doesn't hang up portupgrade. -- --- Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mon, 3 Mar 2008 15:33:00 -0500 Wesley Shields [EMAIL PROTECTED] wrote: On Mon, Mar 03, 2008 at 03:01:00PM -0500, Vivek Khera wrote: On Mar 3, 2008, at 12:27 PM, Wesley Shields wrote: I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. I'll take that as a bug report :-) I didn't intend for that to be a bug report. :) It happened to me to start a largish portupgrade and find it stuck on that particular thingy. I think it doesn't prompt it for package building. What about making it an OPTION ? On first install you need to configure postfix so it shouldn't be on by default (personally it's the fifth or so port I install ...), but on portupgrades everything will work. Though I'm not sure which way it should default, on BATCH. And does BATCH apply to package install as well? Honestly, I have not put much thought into it. I was just pointing out that some ports require post-installation questions to be answered. Thanks for your work on postfix, it's always just worked for me. Indeed! From the ports I use I consider it to be one of the best maintained. Many thanks. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect signature.asc Description: PGP signature
Re: interactive ports - the plague
On Mon, 3 Mar 2008 15:01:00 -0500 Vivek Khera [EMAIL PROTECTED] wrote: On Mar 3, 2008, at 12:27 PM, Wesley Shields wrote: I know mail/postfix asks if it should activate itself in /etc/mail/mailer.conf. I'll take that as a bug report :-) Though I'm not sure which way it should default, on BATCH. And does BATCH apply to package install as well? Looking at the script it seems to be implemented already. It goes with defaults in package building or BATCH is set. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Mon, 03 Mar 2008 19:55:52 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: RW wrote: On Mon, 03 Mar 2008 10:24:21 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: I cannot find any policy on interactive ports in the Porters' Handbook. Maybe there aught to be one. Setting BATCH is supposed to prevent genuinely interactive ports from building (that's actually the original purpose of BATCH). But this will also keep the config screens away from me, which can be handled before all builds quite comfortably. Not if you do the config screens before setting BATCH. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
RW wrote: On Mon, 03 Mar 2008 19:55:52 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: RW wrote: On Mon, 03 Mar 2008 10:24:21 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: I cannot find any policy on interactive ports in the Porters' Handbook. Maybe there aught to be one. Setting BATCH is supposed to prevent genuinely interactive ports from building (that's actually the original purpose of BATCH). But this will also keep the config screens away from me, which can be handled before all builds quite comfortably. Not if you do the config screens before setting BATCH. True, I suppose my make.conf will get a couple of new .if blocks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: polypaudio
On 3/3/08, David Southwell [EMAIL PROTECTED] wrote: Hi Hi I have been out of commission for some time due to some health problems. When to ujpgrade and received the forllowing error message can anyone please advise? Thanks david # portupgrade -a Stale dependency: amavisd-new-2.5.3,1 -- p5-DBD-mysql-4.006 -- manually run 'pkgdb -F' to fix, or specify -O to force. [EMAIL PROTECTED] /usr1/samba/sambap/feb/2359_2575_P]# pkgdb -F --- Checking the package registry database Stale origin: 'audio/akode-plugins-polypaudio': perhaps moved or obsoleted. - The port 'audio/akode-plugins-polypaudio' was removed on 2008-01-01 because: Polypaudio is obsolete in favor of pulseaudio - Hint: akode-plugins-polypaudio-2.0.1_1,1 is required by the following package(s): kdemultimedia-3.5.8 kde-3.5.8 akode-2.0.1,1 - Hint: checking for overwritten files... - No files installed by akode-plugins-polypaudio-2.0.1_1,1 have been overwritten by other packages. Deinstall akode-plugins-polypaudio-2.0.1_1,1 ? [no] y --- Deinstalling 'akode-plugins-polypaudio-2.0.1_1,1' pkg_delete: package 'akode-plugins-polypaudio-2.0.1_1,1' is required by these other packages and may not be deinstalled: akode-2.0.1,1 kde-3.5.8 kdemultimedia-3.5.8 ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! akode-plugins-polypaudio-2.0.1_1,1(pkg_delete failed) Command failed [exit code 1]: /usr/local/sbin/pkg_deinstall akode-plugins-polypaudio-2.0.1_1,1 I created a replacement port for akode-plugins-polypaudio, based on a patch I found on the internet to create an akode-plugins-pulseaudio port. I have been using this plugin for a while (Jun 07), and haven't seen any problems with it. See PR 121344. http://www.freebsd.org/cgi/query-pr.cgi?pr=121344 Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
