Re: [gentoo-user] emacs-common-gentoo-1[X] mask
Jorge Morais wrote: Looking at /usr/portage/app-editors/emacs/emacs-22.3-r2.ebuild, I see that it depends unconditionally on app-emacs/emacs-common-gentoo. You cannot eliminate this dependency by changing USE flags. The most natural solution is to tell Portage to accept the package app-emacs/emacs-common-gentoo, even though it is not officially stable. To learn how to do this, read the portage man page and look for package.keywords. For quick, cake recipe instructions: 1) If there is a file named package.keywords in /etc/portage, add to it the line app-emacs/emacs-common-gentoo 2) If there is a directory named package.keywords in /etc/portage, you can create a file in it (the name of this file is irrelevant), and add to this file the line app-emacs/emacs-common-gentoo If there is already some file in /etc/portage/package.keywords, then, at your option, you can either edit this file and add to it the line app-emacs/emacs-common-gentoo or you can create a new file with this line. Thank you very much for your prompt, clear, and comprehensive response. Your suggestion solved the problem. Best regards, John You are welcome. I forgot to stress something: after some version of app-emacs/emacs-common-gentoo at least as recent as 1.0 becomes stable, you may want to remove the line app-emacs/emacs-common-gentoo from the file you have edited, so that Portage will go back to its normal behavior of seeking stable versions of the package. Anyway, using a testing (not officially stable) version of a single, simple package is unlikely to lead to problems. I prefer to use stable, tested package versions in my system, but one small exception for a small and simple package is harmless. Thank you for this tip. I'll keep my eyes open for a stable app-emacs/emacs-common-gentoo version = 1.0. -- John P. Burkett Department of Economics University of Rhode Island Kingston, RI 02881-0808 USA phone (401) 874-9195
[gentoo-user] emacs-common-gentoo-1[X] mask
Starting March 14, whenever I have tried doing emerge -D -uav system the response has included !!! All ebuilds that could satisfy =app-emacs/emacs-common-gentoo-1[X] have been masked. On my x86 box, the response adds - app-emacs/emacs-common-gentoo-1.0 (masked by: ~x86 keyword) On my amd64 machine, the equivalent line is - app-emacs/emacs-common-gentoo-1.0 (masked by: ~amd64 keyword) The dependency listing is as follows: (dependency required by app-editors/emacs-22.3-r2 [installed]) (dependency required by app-emacs/po-mode-0.17 [installed]) (dependency required by sys-devel/gettext-0.17 [installed]) (dependency required by sys-devel/gcc-4.1.2 [installed]) (dependency required by system [argument]) Doing emerge -D -uav world elicits similar messages. I'm not sure whether it would be safer to (a) emerge a masked version of emacs-common-gentoo-1.0 or to (b) alter the dependency structure, eliminating the requirement for emacs-common-gentoo-1.0. Further, I am not sure how to do either one. Suggestions would be much appreciated. John -- John P. Burkett Department of Economics University of Rhode Island Kingston, RI 02881-0808 USA phone (401) 874-9195
Re: [gentoo-user] emacs-common-gentoo-1[X] mask
On Sat, 28 Mar 2009 14:47:56 -0400 John P. Burkett burk...@uri.edu wrote: Starting March 14, whenever I have tried doing emerge -D -uav system the response has included !!! All ebuilds that could satisfy =app-emacs/emacs-common-gentoo-1[X] have been masked. On my x86 box, the response adds - app-emacs/emacs-common-gentoo-1.0 (masked by: ~x86 keyword) On my amd64 machine, the equivalent line is - app-emacs/emacs-common-gentoo-1.0 (masked by: ~amd64 keyword) The dependency listing is as follows: (dependency required by app-editors/emacs-22.3-r2 [installed]) (dependency required by app-emacs/po-mode-0.17 [installed]) (dependency required by sys-devel/gettext-0.17 [installed]) (dependency required by sys-devel/gcc-4.1.2 [installed]) (dependency required by system [argument]) [..] I'm not sure whether it would be safer to (a) emerge a masked version of emacs-common-gentoo-1.0 or to (b) alter the dependency structure, eliminating the requirement for emacs-common-gentoo-1.0. Further, I am not sure how to do either one. Suggestions would be much appreciated. Looking at /usr/portage/app-editors/emacs/emacs-22.3-r2.ebuild, I see that it depends unconditionally on app-emacs/emacs-common-gentoo. You cannot eliminate this dependency by changing USE flags. The most natural solution is to tell Portage to accept the package app-emacs/emacs-common-gentoo, even though it is not officially stable. To learn how to do this, read the portage man page and look for package.keywords. For quick, cake recipe instructions: 1) If there is a file named package.keywords in /etc/portage, add to it the line app-emacs/emacs-common-gentoo 2) If there is a directory named package.keywords in /etc/portage, you can create a file in it (the name of this file is irrelevant), and add to this file the line app-emacs/emacs-common-gentoo If there is already some file in /etc/portage/package.keywords, then, at your option, you can either edit this file and add to it the line app-emacs/emacs-common-gentoo or you can create a new file with this line. -- Software is like sex: it is better when it is free. --Linus Torvalds
Re: [gentoo-user] emacs-common-gentoo-1[X] mask
Jorge Morais wrote: On Sat, 28 Mar 2009 14:47:56 -0400 John P. Burkett burk...@uri.edu wrote: Starting March 14, whenever I have tried doing emerge -D -uav system the response has included !!! All ebuilds that could satisfy =app-emacs/emacs-common-gentoo-1[X] have been masked. On my x86 box, the response adds - app-emacs/emacs-common-gentoo-1.0 (masked by: ~x86 keyword) On my amd64 machine, the equivalent line is - app-emacs/emacs-common-gentoo-1.0 (masked by: ~amd64 keyword) The dependency listing is as follows: (dependency required by app-editors/emacs-22.3-r2 [installed]) (dependency required by app-emacs/po-mode-0.17 [installed]) (dependency required by sys-devel/gettext-0.17 [installed]) (dependency required by sys-devel/gcc-4.1.2 [installed]) (dependency required by system [argument]) [..] I'm not sure whether it would be safer to (a) emerge a masked version of emacs-common-gentoo-1.0 or to (b) alter the dependency structure, eliminating the requirement for emacs-common-gentoo-1.0. Further, I am not sure how to do either one. Suggestions would be much appreciated. Looking at /usr/portage/app-editors/emacs/emacs-22.3-r2.ebuild, I see that it depends unconditionally on app-emacs/emacs-common-gentoo. You cannot eliminate this dependency by changing USE flags. The most natural solution is to tell Portage to accept the package app-emacs/emacs-common-gentoo, even though it is not officially stable. To learn how to do this, read the portage man page and look for package.keywords. For quick, cake recipe instructions: 1) If there is a file named package.keywords in /etc/portage, add to it the line app-emacs/emacs-common-gentoo 2) If there is a directory named package.keywords in /etc/portage, you can create a file in it (the name of this file is irrelevant), and add to this file the line app-emacs/emacs-common-gentoo If there is already some file in /etc/portage/package.keywords, then, at your option, you can either edit this file and add to it the line app-emacs/emacs-common-gentoo or you can create a new file with this line. Thank you very much for your prompt, clear, and comprehensive response. Your suggestion solved the problem. Best regards, John -- John P. Burkett Department of Economics University of Rhode Island Kingston, RI 02881-0808 USA phone (401) 874-9195
Re: [gentoo-user] emacs-common-gentoo-1[X] mask
Looking at /usr/portage/app-editors/emacs/emacs-22.3-r2.ebuild, I see that it depends unconditionally on app-emacs/emacs-common-gentoo. You cannot eliminate this dependency by changing USE flags. The most natural solution is to tell Portage to accept the package app-emacs/emacs-common-gentoo, even though it is not officially stable. To learn how to do this, read the portage man page and look for package.keywords. For quick, cake recipe instructions: 1) If there is a file named package.keywords in /etc/portage, add to it the line app-emacs/emacs-common-gentoo 2) If there is a directory named package.keywords in /etc/portage, you can create a file in it (the name of this file is irrelevant), and add to this file the line app-emacs/emacs-common-gentoo If there is already some file in /etc/portage/package.keywords, then, at your option, you can either edit this file and add to it the line app-emacs/emacs-common-gentoo or you can create a new file with this line. Thank you very much for your prompt, clear, and comprehensive response. Your suggestion solved the problem. Best regards, John You are welcome. I forgot to stress something: after some version of app-emacs/emacs-common-gentoo at least as recent as 1.0 becomes stable, you may want to remove the line app-emacs/emacs-common-gentoo from the file you have edited, so that Portage will go back to its normal behavior of seeking stable versions of the package. Anyway, using a testing (not officially stable) version of a single, simple package is unlikely to lead to problems. I prefer to use stable, tested package versions in my system, but one small exception for a small and simple package is harmless. -- Software is like sex: it is better when it is free. --Linus Torvalds
