Re: emacs22 and portsdb
Hi, I have been having trouble with emacs22 also. I am using FreeBSD 6.2-RELEASE-p7. I did the upgrade as described in the updating notes. I use emacs plus auctex slime quack emacs-w3m Everything was upgraded properly. However, no portsdb -Uu generates errors. Therefore, I have remove EMACS_PORT_NAME=emacs22 from /etc/make.conf and now portsdb -Uu works without a problem. However, if I remove any of the ports such as auctex and then reinstall it, portinstall will try to install emacs21 again which conflicts with emacs22. I am stuck. If I leave EMACS_PORT_NAME=emacs22 in /etc/make.conf then dependencies work but portsdb -Uu fails. If I remove EMACS_PORT_NAME=emacs22 from /etc/make.conf then portsdb -Uu works but the dependencies are messed up. I even went as far as to delete emacs with pkg_delete -r emacs-22.1 and tried installing everything from scratch. However the dependencies are still messed up. Does anybody have a solution to this problem? Thanks, Arend van der Veen Matthew Seaman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Duane Winner wrote: We've been having a problem with generating the ports Index ever since upgrading to emacs22. As per /usr/ports/UPDATING, we added EMACS_PORT_NAME=*emacs22* to /etc/make.conf Errr --- that should probably read: EMACS_PORT_NAME=emacs22 You certainly don't need the asterisks there. In any case, setting this variable will screw up indexing, because a number of e-lisp ports will try and append the EMACS_PORT_NAME to their package origin if it is set. However not all the ports that do that also have a slave port 'foo-emacs22' hence the problems with building the INDEX. The best answer is don't set EMACS_PORT_NAME in /etc/make.conf -- emacs22 is the default now anyhow. The INDEX will build just fine, and the various e-lisp packages seem to work OK as well, so long as you've reinstall all the e-lisp packages once you've upgraded from emacs21 to emacs22. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGql0a8Mjk52CukIwRCJkgAJ0fh9qkl4eWFQRwrrG8DIwAOqUmlACeMT19 8AWFPYKQdh8Fvko14TCwyxs= =vZLj -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: emacs22 and portsdb
On Fri, Jul 27, 2007 at 10:01:14PM +0100, Matthew Seaman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Duane Winner wrote: We've been having a problem with generating the ports Index ever since upgrading to emacs22. As per /usr/ports/UPDATING, we added EMACS_PORT_NAME=*emacs22* to /etc/make.conf Errr --- that should probably read: EMACS_PORT_NAME=emacs22 You certainly don't need the asterisks there. In any case, setting this variable will screw up indexing, because a number of e-lisp ports will try and append the EMACS_PORT_NAME to their package origin if it is set. However not all the ports that do that also have a slave port 'foo-emacs22' hence the problems with building the INDEX. The best answer is don't set EMACS_PORT_NAME in /etc/make.conf -- emacs22 is the default now anyhow. The INDEX will build just fine, and the various e-lisp packages seem to work OK as well, so long as you've reinstall all the e-lisp packages once you've upgraded from emacs21 to emacs22. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGql0a8Mjk52CukIwRCJkgAJ0fh9qkl4eWFQRwrrG8DIwAOqUmlACeMT19 8AWFPYKQdh8Fvko14TCwyxs= =vZLj -END PGP SIGNATURE- Thanks! I've commented out the EMACS_PORT_NAME=emacs22 entry in /etc/make.conf. All seems well except on portupgrade -a, I'm getting ** Detected a package name change: apel-emacs22 (editors/apel) - 'apel-emacs21' (editors/apel) ** No need to upgrade 'apel-emacs22-10.7_1' (= apel-emacs21-10.7_1). (specify -f to force) ** Detected a package name change: flim-emacs22 (editors/flim) - 'flim-emacs21' (editors/flim) ** No need to upgrade 'flim-emacs22-1.14.8_1' (= flim-emacs21-1.14.8_1). (specify -f to force) ** Detected a package name change: mule-ucs-emacs22 (converters/mule-ucs) - 'mule-ucs-emacs21' (converters/mule-ucs) ** No need to upgrade 'mule-ucs-emacs22-0.85.r3_1' (= mule-ucs-emacs21-0.85.r3_1). (specify -f to force) ** Detected a package name change: semi-emacs22 (editors/semi) - 'semi-emacs21' (editors/semi) ** No need to upgrade 'semi-emacs22-1.14.6_2' (= semi-emacs21-1.14.6_2). (specify -f to force) ** Detected a package name change: emacs-w3m-emacs22 (www/emacs-w3m) - 'emacs-w3m-emacs21' (www/emacs-w3m) ** No need to upgrade 'emacs-w3m-emacs22-1.4.4_3' (= emacs-w3m-emacs21-1.4.4_3). (specify -f to force) Both running portupgrade -f apel-emacs22-10.7_1 etc. and running portupgrade -fr emacs failed. Many thanks for any ideas! Cheers, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: emacs22 and portsdb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Duane Winner wrote: We've been having a problem with generating the ports Index ever since upgrading to emacs22. As per /usr/ports/UPDATING, we added EMACS_PORT_NAME=*emacs22* to /etc/make.conf Errr --- that should probably read: EMACS_PORT_NAME=emacs22 You certainly don't need the asterisks there. In any case, setting this variable will screw up indexing, because a number of e-lisp ports will try and append the EMACS_PORT_NAME to their package origin if it is set. However not all the ports that do that also have a slave port 'foo-emacs22' hence the problems with building the INDEX. The best answer is don't set EMACS_PORT_NAME in /etc/make.conf -- emacs22 is the default now anyhow. The INDEX will build just fine, and the various e-lisp packages seem to work OK as well, so long as you've reinstall all the e-lisp packages once you've upgraded from emacs21 to emacs22. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGql0a8Mjk52CukIwRCJkgAJ0fh9qkl4eWFQRwrrG8DIwAOqUmlACeMT19 8AWFPYKQdh8Fvko14TCwyxs= =vZLj -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
