Re: value of maintaining emacs-mode packages in ports

2014-11-23 Thread Roland Smith
On Sun, Nov 23, 2014 at 12:32:14AM +0100, Christopher J. Ruwe wrote:
 I am well aware that very probably I might be starting a rant thread,
 however, I am genuinely interested in opinions from the community.
 
 Since version 24, Emacs, the very good operating system missing only a
 decent editor, has developed a package manager for Emacs
 extensions. Some good repos exist, packages are usually installed to
 ~/.emacs.d and I have come to really enjoy that way of installing
 packages.
 
 In that light and as the ports maintainer of math/ess, the Emacs
 speaks statistics R-mode of emacs, I am asking myself specifically
 whether I add any real benefit in maintaining math/ess. More
 generally, I am interested in community answers as to whether it is
 really useful to maintain Emacs-extension-packages in ports.
 
 Thanks for your thoughts, cheers,

It might help to see this question in a broader context.

There are several communities that have there own repositories/package
managers these days, e.g:

* TeX
* Perl
* Python
* Ruby
* Node
* Emacs

Yet the maintainers of the ports system go through the effort of maintaining
ports for a lot of these packages, even though it might strictly speaking be
considered a duplication of effort.

There are at least two big reasons that I can think of;

1) FreeBSD specific patches are necessary to build a package. (I.e. every port
   that has a files subdirectory.) The ports tree is arguably the right place
   for that. The best case would be that such changes are merged upstream, but
   that doesn't always happen.
2) A foreign package might depend on a FreeBSD port or the other way
   around. How could this be handled properly if not in the ports tree?
   So by its very nature, if you want to reap the benefits of the ports
   infrastructure for your package, you have to *use* said infrastructure.

Packages that *can* install in a user's $HOME directory and have no
non-obvious dependencies are the exception to this rule, I think. No one will
expect e.g. a vim bundle to do anything useful when vim is not installed!

But such packages are obviously only available to the user that has installed
them. So for a multi-user installation a port would still make more sense.


Roland
-- 
R.F.Smith   http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93  FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)


pgp2YDWbnD0Jc.pgp
Description: PGP signature


Re: CFT: Update to xf86-video-ati 7.5.0

2014-10-28 Thread Roland Smith
On Mon, Oct 27, 2014 at 10:26:32AM +0100, Jean-Sébastien Pédron wrote:
 Hi!
 
 Before updating xf86-video-ati to 7.5.0, we would like some people to
 try it out. The reason is that 7.4.0 was crashing for several users, so
 we want to be sure it's fixed in 7.5.0.
 
 Here's patch:
 https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.0.patch
 
 To apply it:
   cd /usr/ports
   patch -p1  /path/to/ports-xf86-video-ati-7.5.0.patch
 
 Then update x11-drivers/xf86-video-ati with your method of choice.

Works fine with Radeon X1650 (ChipID = 0x71c1) on FreeBSD 10.1-PRERELEASE #0 
r273434
(amd64, GENERIC kernel). All ports updated on 2014-10-26.


Roland
-- 
R.F.Smith   http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93  FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)


pgpHuJ03Fv_XO.pgp
Description: PGP signature


Re: optionsng ignores /var/db/ports/portname/options

2012-06-04 Thread Roland Smith
On Sun, Jun 03, 2012 at 11:54:06PM +0200, Baptiste Daroussin wrote:
  You found a nice bug.
  
  The options file is read the thing is that the UNIQUENAME is changed is
  py-py-stl when the optionsfile is read and it is py27-py-stl when it is 
  written.
  
  I don't know why yet, I'll fix it asap.
  
  regards,
  Bapt
 
 FYI the bug you found also happen with python and rubygem ports, it can also
 happen with apache ports, in fact any ports depending on bsd.*.mk where
 bsd.*.mk defines the pkgnameprefix.
 
 nothing directly related to optionsNG a good example of workaround is: look
 at py-yaml
 
 You can have multiple workarounds:
 first one: define OPTIONSFILE in your ports like py-yaml

I did that, and it works fine. It seems the a simple solution.

 second one: replace bsd.port.options.mk by bsd.port.pre.mk (do not forget in
 that case the bsd.port.post.mk in the end)

I had pre and post in my port makefile: it didn't work.

Thanks for your help!

Roland
-- 
R.F.Smith   http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpyNAgL7wzZx.pgp
Description: PGP signature


optionsng ignores /var/db/ports/portname/options

2012-06-03 Thread Roland Smith
[Please cc me, since I'm not subscribed to this list. I originally asked this
on questions@.]

Hi,

With the release of the new options framework for ports, I've run into a
problem trying to convert one of my ports.

The nature of the problem is that the port seems to ignore the setting stored
in /var/db/ports/portname/options:

I've used 'make config' to set the PYCAIRO option to on;

slackbox# cat /var/db/ports/py27-py-stl/options
# This file is auto-generated by 'make config'.
# Options for py27-py-stl-3.1
_OPTIONS_READ=py27-py-stl-3.1
_FILE_COMPLETE_OPTIONS_LIST=PYCAIRO
OPTIONS_FILE_SET+=PYCAIRO

But the port seems to ignore it:

slackbox# make showconfig
=== The following configuration options are available for py27-py-stl-3.1:
 PYCAIRO=off: Use (py)Cairo to enable stl2pdf
=== Use 'make config' to modify these settings

slackbox# make -V PORT_OPTIONS
DOCS EXAMPLES NLS

Every time I do 'make config', the PYCAIRO option will be unset, even if it
shows as set in /var/db/ports/portname/options!

My port Makefile is as follows:
 port Makefile 
# New ports collection makefile for:py-stl
# Date created: 28 Dec 2011
# Whom: rsm...@xs4all.nl
#
# $FreeBSD$

PORTNAME=   py-stl
PORTVERSION=3.1
CATEGORIES= graphics python
MASTER_SITES=   http://rsmith.home.xs4all.nl/software/
PKGNAMEPREFIX=  ${PYTHON_PKGNAMEPREFIX}

MAINTAINER= rsm...@xs4all.nl
COMMENT=Converts STL models to POV-Ray meshes or PostScript/PDF 
images

USE_ZIP=YES
USE_PYTHON= 2.5+
USE_PYDISTUTILS=YES

CONFLICTS=  stl2pov-[0-9]*

MAN1=   stl2ps.1 stlinfo.1

OPTIONS_DEFINE= PYCAIRO
PYCAIRO_DESC=   Use (py)Cairo to enable stl2pdf

.include bsd.port.options.mk

.if ${PORT_OPTIONS:MPYCAIRO}
RUN_DEPENDS+=   
${PYTHON_PKGNAMEPREFIX}cairo1.8:${PORTSDIR}/graphics/py-cairo
MAN1+=  stl2pdf.1
PLIST_SUB+= STL2PDF=
.else
PLIST_SUB+= STL2PDF=@comment 
.endif

NO_BUILD=   YES

post-install:
.if ${PORT_OPTIONS:MPYCAIRO}
@${INSTALL_MAN} ${WRKSRC}/stl2pdf.1 ${MANPREFIX}/man/man1
@${MV} ${PREFIX}/bin/stl2pdf.py ${PREFIX}/bin/stl2pdf
.else
@${RM} -f ${PREFIX}/bin/stl2pdf.py
@${RM} -f  ${MANPREFIX}/man/man1/stl2pdf.1*
.endif
@${INSTALL_MAN} ${WRKSRC}/stl2ps.1 ${MANPREFIX}/man/man1
@${INSTALL_MAN} ${WRKSRC}/stlinfo.1 ${MANPREFIX}/man/man1
@${MV} ${PREFIX}/bin/stl2ps.py  ${PREFIX}/bin/stl2ps
@${MV} ${PREFIX}/bin/stl2pov.py ${PREFIX}/bin/stl2pov
@${MV} ${PREFIX}/bin/stlinfo.py ${PREFIX}/bin/stlinfo
@${MV} 
${PYTHON_SITELIBDIR}/py_stl-${PORTVERSION}-py${PYTHON_VER}.egg-info 
${PYTHON_SITELIBDIR}/${PYDISTUTILS_EGGINFO}

.include bsd.port.mk
 port Makefile 

I've looked at other ports makefiles and see no obvious defects. Help?

Roland
-- 
R.F.Smith   http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpDq8la7PwLF.pgp
Description: PGP signature


Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-14 Thread Roland Smith
On Sun, Aug 14, 2011 at 01:05:34PM +0200, Olivier Smedts wrote:
  Just got a notebook, build with the old gcc 4.2 of the system FreeBSD
  9.0/amd64 -r224579: portsnap works as expected.
 
  I will build a most recent system on that box (with systems's outdated gcc
  4.2) and I'll report if the problem is still present.
 
  By the way: My boxes of failure are all built with CLANG.
 
  Oliver
 
 Trying again today, with my 9.0-BETA1 amd64 box built with clang.
 
 Not the same error, but the same kind when using portsnap extract :
 /usr/ports/lang/p5-JavaScript-Value-Escape/
 /usr/ports/lang/p5-JavaScript/
 /usr/ports/lang/p5-List-MoreUtils/
 /usr/ports/lang/p5-Modern-Perl/
 /usr/ports/lang/p5-POE-Component-Hailo/
 files/b54a58da6d23d31f19a9105f70af03ef797aba8db6bdbc03d6deb72e62011d56.gz
 not found -- snapshot corrupt.
 
 This file is not present in /var/db/portsnap/files/.
 
 # ll /var/db/portsnap/files/ | wc -l
22862
 
 This was after removing /var/db/portsnap/files/ and
 /var/db/portsnap/t* and a fresh portsnap fetch, on the portsnap5
 mirror.
 
 # fetch 
 http://portsnap5.freebsd.org/s/c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz
 # tar tf c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz
 | grep b54a58
 nothing...

I tried the same on 8.2-RELEASE amd64, built with gcc 4.2; _also_ nothing!

Isn't the name of the snapshot supposed to be the SHA256 of the tarball?
because it doesn't match;

# sha256 c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz 
SHA256 (c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz) = 
c6dee407367784681374dae8375f4c4cdbf425338c7e73cf72c673291d1d0473
# gunzip c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz 
# sha256 c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tar 
SHA256 (c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tar) = 
f49e05296accfc0457a89157288039eb212f6e57b2d694e05ca09f9f5c1e69f6

The mystery deepens...

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpDX0d7ZhdcU.pgp
Description: PGP signature


Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-13 Thread Roland Smith
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
 On 08/12/11 22:54, Roland Smith wrote:
  On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
  files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz

Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpG6q3xoHrnr.pgp
Description: PGP signature


Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-12 Thread Roland Smith
On Fri, Aug 12, 2011 at 05:46:37PM +0200, Hartmann, O. wrote:
 Since today, I can not update my ports tree due to this error as follows.
 This happens on all boxes running FreeBSD, the version of the OS (FBSD 
 8.2/9.0) doesn't
 matter. What's up with the ports collection?

Probably nothing.

 files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not 
 found -- snapshot corrupt.

This looks like a portsnap error. Remove everything in /var/db/portsnap, and
run 'portsnap fetch extract'.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgp9QcHByGZXX.pgp
Description: PGP signature


Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-12 Thread Roland Smith
On Fri, Aug 12, 2011 at 07:38:06PM +0200, Olivier Smedts wrote:
 2011/8/12 Roland Smith rsm...@xs4all.nl:
  On Fri, Aug 12, 2011 at 05:46:37PM +0200, Hartmann, O. wrote:
  Since today, I can not update my ports tree due to this error as follows.
  This happens on all boxes running FreeBSD, the version of the OS (FBSD
  8.2/9.0) doesn't
  matter. What's up with the ports collection?
 
  Probably nothing.
 
  files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz 
  not
  found -- snapshot corrupt.
 
  This looks like a portsnap error. Remove everything in /var/db/portsnap, and
  run 'portsnap fetch extract'.
 
 Same error here and after removing all files in /var/db/portsnap/
 except pub.ssl and serverlist*.

Did you clean out the files subdirectory as well? Try and remove
/var/db/portsnap completely.

 files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz

This file is relatively recent; When I used portsnap yesterday, it wasn't
there, and now it is.

Have you fscked the volume that contains /var? If not I suggest you do. You
might be looking at filesystem corruption.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgp3PU2kR93zk.pgp
Description: PGP signature


Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-12 Thread Roland Smith
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
  files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
  This file is relatively recent; When I used portsnap yesterday, it wasn't
  there, and now it is.
 I do a postrmaster on a nearly daily basis. This occured this morning 
 (German standard time) to me the first time.

I did a portsnap just before my previous mail. It downloaded and extracted the
particular file without problem.

  Have you fscked the volume that contains /var? If not I suggest you do. You
  might be looking at filesystem corruption.
 No I did not. If this is a inconsistent filesystem (I thought about this 
 also), then it
 has occured on ALL(!) FreeBSD 9.0-CURRENT/amd64 boxes over night (this i 
 why I thought about the filesystem, since the FreeBSD 8.2/amd64-boxes do 
 not show this problem as I mentioned at the start of the post, my mistake).

Another data-point: I'm on 8.2-RELEASE amd64 as well and it doesn't show a
problem. So it could well be a CURRENT specific problem. But I would think
that the filesystem code would be pretty mature by now. Maybe some changes in
VFS?

 I'll force a fsck as soon as possible. I started the boxes already and 
 they didn't show up any unclean filesystem so far ...

Since portsnap cannot find the file in question, I assume you have checked
that it existed and that it was a normal file etc?

Could it be a hardware issue? Some time ago I began to have random filesystem
corruption and lockups. After cleaning out two years worth of dust out of the
machine in question it now runs fine again.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpdTakzRbmQY.pgp
Description: PGP signature


Re: xorg-server 1.9.3 and 1.10.0

2011-03-09 Thread Roland Smith
On Thu, Mar 10, 2011 at 03:11:48AM +0800, Martin Wilke wrote:
 just for the record, i manage to get xorg-server 1.9.3 and 1.10.0 to work,
 also drm, and dri works very well,
 
 screens and logs gives here:
 http://people.freebsd.org/~miwi/xorg76/

Seems like you got transparancy to work. :-) A bit hard on the eyes, though.

 I'll cleanup all the mess and commit all stuff to the xorg-dev repo. Maybe
 someone have intressing to test it.

Would it work on 8.2 amd64? If so I can test it. Are there more ports
that need re-building except the server itself? 

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgppO9hZE4mDf.pgp
Description: PGP signature


Re: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating

2010-12-26 Thread Roland Smith
On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote:
Something I'm missing here? A fix would be nice, I should be used to it
though- ImageMagick _always_ has issues for me. I just thought it'd be
nice to get it updated for once- it looked so close :)
   
  I'm getting something similar, have been for a couple of weeks:
 
  ** Port marked as IGNORE: graphics/ImageMagick:
  OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with 
  threads or undefine WITH_IMAGEMAGICK_PERL
  ** Listing the failed packages (-:ignored / *:skipped / !:failed)
  - graphics/ImageMagick (marked as IGNORE)
 
  (Follow-ups redirected to ports@, or I tried to.)
 
 
 Hmm. I'm not alone then. I'll do some poking then and see what comes 
 up... :)
 
 Any hints guys?

Try building ImageMagick without perl support. Works for me, with EXR, but
haven't tested with Djvu;

cd /usr/ports/graphics/ImageMagick
make config
 ┌┐ 
 │ Options for ImageMagick 6.6.5.10   │ 
 │ ┌^(-)┐ │ 
...
 │ │[X] IMAGEMAGICK_OPENEXR  OpenEXR support (needs threads)│ │ 
 │ │[X] IMAGEMAGICK_OPENMP   OpenMP for SMP (needs threads) │ │ 
 │ │[ ] IMAGEMAGICK_PDF  PDF format support │ │ 
 │ │[ ] IMAGEMAGICK_PERL Perl support   │ │ 
...

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpTVxAseawVV.pgp
Description: PGP signature


Re: testing rnoland's xorg upgrade patch -- error

2009-01-08 Thread Roland Smith
On Thu, Jan 08, 2009 at 05:36:38PM -0500, Robert Noland wrote:
 I just rolled up a new patchset.  This has not been through tinderbox
 yet, so you have been warned...  This update should pretty much have us
 current with all released xorg bits.
 
 http://people.freebsd.org/~rnoland/xorg-update-010809.patch.bz2

Looking over the patch, why is the glut library version changing from
libglut.so.4 to libglut.so.3?

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpbMs7VteTDh.pgp
Description: PGP signature


Re: amd64/121951: Javascript bug in _amd64_ version of Mozilla-Firefox

2008-03-22 Thread Roland Smith
The following reply was made to PR amd64/121951; it has been noted by GNATS.

From: Roland Smith [EMAIL PROTECTED]
To: Bill Squire [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: amd64/121951: Javascript bug in _amd64_ version of
Mozilla-Firefox
Date: Sat, 22 Mar 2008 13:55:32 +0100

 --Kj7319i9nmIyA2yE
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Sat, Mar 22, 2008 at 03:52:30AM +0100, Bill Squire wrote:
 =20
  Number: 121951
  Category:   amd64
  Synopsis:   Javascript bug in _amd64_ version of Mozilla-Firefox
  Confidential:   no
  Severity:   non-critical
  Priority:   medium
  Responsible:freebsd-amd64
  State:  open
  Quarter:   =20
  Keywords:  =20
  Date-Required:
  Class:  sw-bug
  Submitter-Id:   current-users
  Arrival-Date:   Sat Mar 22 03:30:01 UTC 2008
  Closed-Date:
  Last-Modified:
  Originator: Bill Squire
  Release:FreeBSD 7.0-STABLE amd64
  Organization:
  Billsf Holding BV / Squire for Hire=09
  Environment:
  System: FreeBSD curacao.billsf.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed =
 Mar 12 16:30:16 CET 2008 [EMAIL PROTECTED]:/usr/obj/pkg/src_7/src/sys=
 /CURACAO-SMP amd64  Xorg-xorg-7.3_1 with xf86-video-ati-6.7.196 for ATI Rad=
 eon X550 (RV370)
   5B63 (PCIE) with XFCE (Gnome apps and some KDE apps)
 
 FreeBSD slackbox.xs4all.nl 7.0-STABLE FreeBSD 7.0-STABLE #0: Fri Feb 29 01:=
 45:32 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/RFS  amd64
 
 xorg-server-1.4_6,1 and xf86-video-ati-6.8.0_1 on a Radeon 9250 (RV280).
 
 firefox-2.0.0.12_1,1 with the following OPTIONS:
 WITH_NEWTAB=3Dtrue
 WITHOUT_SMB=3Dtrue
 WITH_DEBUG=3Dtrue
 WITHOUT_LOGGING=3Dtrue
 WITH_OPTIMIZED_CFLAGS=3Dtrue
 
 JavaScript is enabled, but all the options under 'advanced' are off.
 
  How-To-Repeat:
  goto: http://maps.google.com/ and note there are NO maps -- anywhere
  100% repeatable -- problem has developed over the past six months.  =
 =20
 
 Shows fine here. No errors in the error console, just some warnings. It
 _does_ show maps.
 =20
  goto: http://slashdot.org/, login and try to Retrieve more of 
  (at the bottom of the page)
  Try to set preferences or any other 'ajax-style' window=20
  100% repeatable -- has developed over 1/2 a year.=20
 
 Other than the 'pop-up' windows are bloody slow, I see nothing wrong
 with them.
 
  http://ns.nl/ has very good error recovery in its scripts -- works.
  error: 'u has no properties' (no noticable consequences) =
 =20
 
 A lot of warnings concerning css, but no errors here. Works fine.
 
 Roland
 --=20
 R.F.Smith   http://www.xs4all.nl/~rsmith/
 [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
 pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
 
 --Kj7319i9nmIyA2yE
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.8 (FreeBSD)
 
 iEYEARECAAYFAkflAcQACgkQEnfvsMMhpyVg2ACffyu1kM1A/FhMTZ3ZtuAKaFAt
 Z88AoKowxabo9+c1unfkk29hlDZqbfAn
 =+ad6
 -END PGP SIGNATURE-
 
 --Kj7319i9nmIyA2yE--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Upgrading to amd64 requires recompilation of ports?

2007-06-17 Thread Roland Smith
On Sat, Jun 16, 2007 at 06:21:40PM -0400, Indigo 23 wrote:
  Does anyone think that its worth the hassle? If you do manage to get
  it up and running, will you see any noticeable advantages or is it
  better to just stick with i386? The only caveat that I can see is a
  recompilation of all the ports.  Any thoughts?

You don't really _need_ it unless you've got more than four gigs of RAM
and are routinely running out of memory on i386. Then again, I installed
amd64 instead of i386 because I could. :-) No regrets so far.

Some stuff like binary drivers, flash player, is not available on
amd64 (not necessarily a bad thing :-). I think i386 has more ports
available as packages.

Amd 64 will use some more disk space and RAM.

Doing a clean reinstall instead of an upgrade will probably less of a hassle.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpAC0HPmdICd.pgp
Description: PGP signature