Re: Dislike the way port conflicts are handled now
Greg Larkin píše v so 16. 01. 2010 v 18:02 -0500: Here is the original post: http://www.mail-archive.com/freebsd-questions@freebsd.org/msg227363.html I will agree that `portupgrade -o` is way too useful feature. I'd vote for reverting to the old behaviour. I thought portmgr might have some insight into additional reasons for making the change, such as fixing a problem with pointyhat builds, etc. At the moment, I'm neutral on the change, since it hasn't caused me any grief, but I did some research for the folks who posted the original questions. It was done because someone thought it is a good idea and submitted a PR about it. -- Pav Lucistnik p...@oook.cz p...@freebsd.org I can't do that, that would make sense. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Dislike the way port conflicts are handled now
Greg Larkin píše v so 16. 01. 2010 v 13:58 -0500: That's exactly what I proposed. The bsd.port.mk could be patched to support a new variable (EARLY_CONFLICT_CHECK=yes or somesuch) that shifts the check-conflict target from its old position (part of the install sequence) to its new position (fetch?). The default behavior (no mods to /etc/make.conf) would revert to the old conflict checking method. This may be something for portmgr@ to chime in on, and I'm cc'ing them now. There could be other reasons for this change that I'm unaware of. What is the particular scenario that the new conflicts handling broke for you? Often you really want to ignore locally installed packages and then it's better to override LOCALBASE to /nonex or something similar, instead of disabling conflict handling... -- Pav Lucistnik p...@oook.cz p...@freebsd.org It's the classic Microsoft security-bulletin formula: The vulnerability is important (never dangerous); you have nothing to fear and no reason to regret trusting us; we have no intention of apologizing for it or even explaining it adequately; now go get your patch, shut up, and be grateful nothing bad has happened. -- The Register signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Fwd: troubles with libxslt and libxml2 from ports.
Jeff MacDonald píše v út 15. 05. 2007 v 13:03 -0400: /usr/bin is set in my path first. So for now I've just renamed /usr/bin/xml2-config to /usr/bin/xml2-config.dist and things seem to be working fine. There is no /usr/bin/xml2-config in FreeBSD, and never was. Get rid of it. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] Any Palm app requiring an 90+ page manual has lost its vision. -- words about DateBk4 on Action Names list signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: port tree fetch errors
Tofik Suleymanov píše v út 27. 12. 2005 v 22:24 +: My ports-supfile is: *default host=cvsup.nl.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all i do: cvsup -g -z -L 2 /etc/ports-supfile and get this: Updating collection ports-all/cvs Cannot calculate checksum for /usr/ports/devel/boost/pkg-plist: Input/output error Cannot calculate checksum for /usr/ports/devel/clint/files/patch-python.h: Input/output error Cannot calculate checksum for /usr/ports/devel/crossgo32-djgpp2/pkg-plist: Input/output error Checkout ports/devel/Makefile Cannot calculate checksum for /usr/ports/devel/elib/files/patch-aa: Input/output error Can you read the content of those files? I'd bet you got either corrupted filesystem, or your hard drive is dying. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] With a 10 MHz 386 the downloading speed would most likely drop to a crawl or stop with the decoding process etc. I think most 10MHz 386 users are quite accustomed to things dropping to a crawl. signature.asc Description: Toto je digitálně podepsaná část zprávy
