Re: [gentoo-user] Emerge question
Hello, this is what I was wondering. I am thinking of doing something on top on emerge to be able to build non-dependant package at the same time for the same target. I think it would be more efficient than a 'make -jx' especially for the 'world' target. Thomas If I understand what you are asking, I would suppose that starting # emerge C in one terminal, and then # emerge B in another, will result in package B being built twice, as, if I'm not mistaken, portage only looks at dependancies once If you are certain that packages you want to emerge have no comon dependancies or dependant functions, it is generally safe to emerge them at the same time. If you are not positive, don't take the chance. Fixing problems you might create may more than use up the time you might have saved. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Emerge question
[EMAIL PROTECTED] wrote: Hello, I would like some information about emerge. I want to get the package C. C depends of the package A and the package B. The package B does not depend on the package A or vice-versa. I do 'emerge C': emerge will build A, then B, then C. When emerge is building A, I run 'emerge B'. So, B is builded at the same time than A. Will 'emerge C' will build B again after A or will it emerge directly C ? Thank very much, Thomas -- [EMAIL PROTECTED] mailing list Who's on first... ;) -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Emerge question
On Tuesday 30 December 2003 09:06 pm, Ben Sparks wrote: [EMAIL PROTECTED] wrote: Hello, I would like some information about emerge. I want to get the package C. C depends of the package A and the package B. The package B does not depend on the package A or vice-versa. I do 'emerge C': emerge will build A, then B, then C. When emerge is building A, I run 'emerge B'. So, B is builded at the same time than A. Will 'emerge C' will build B again after A or will it emerge directly C ? Thank very much, Thomas -- [EMAIL PROTECTED] mailing list Who's on first... ;) -- [EMAIL PROTECTED] mailing list If I understand what you are asking, I would suppose that starting # emerge C in one terminal, and then # emerge B in another, will result in package B being built twice, as, if I'm not mistaken, portage only looks at dependancies once If you are certain that packages you want to emerge have no comon dependancies or dependant functions, it is generally safe to emerge them at the same time. If you are not positive, don't take the chance. Fixing problems you might create may more than use up the time you might have saved. -- Regards, Ernie 100% Microsoft and Intel free -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge question
On Tue, Sep 02, 2003 at 03:22:19PM +0200, Philippe Van Hecke wrote: I am playing with many kernel version. And must emerge alsa-driver,nvidia-kernel for each kernel i install. My question is there is way when i emerge these two modules, to tell, with command line option to not unmerge the previous merged modules ? I know that when i do emerge i have arround 5 second to tell to portage to not umerge. But i would like to have this done automaticly. I have built a binary package of the also module and let portage clean everything. After instaling a new kernel I simply reinstall the binary package again. Thomas pgp0.pgp Description: PGP signature
Re: [gentoo-user] emerge question
On Wednesday 03 September 2003 10:26, Thomas Buntrock wrote: On Tue, Sep 02, 2003 at 03:22:19PM +0200, Philippe Van Hecke wrote: I am playing with many kernel version. And must emerge alsa-driver,nvidia-kernel for each kernel i install. My question is there is way when i emerge these two modules, to tell, with command line option to not unmerge the previous merged modules ? I know that when i do emerge i have arround 5 second to tell to portage to not umerge. But i would like to have this done automaticly. I have built a binary package of the also module and let portage clean everything. After instaling a new kernel I simply reinstall the binary package again. Thomas If you do that with a new kernel version you can break version dep. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge question
begin quote On Tue, 2 Sep 2003 15:22:19 +0200 Philippe Van Hecke [EMAIL PROTECTED] wrote: I am playing with many kernel version. And must emerge alsa-driver,nvidia-kernel for each kernel i install. My question is there is way when i emerge these two modules, to tell, with command line option to not unmerge the previous merged modules ? I know that when i do emerge i have arround 5 second to tell to portage to not umerge. But i would like to have this done automaticly. An ugly hack is to remove the installed package information in /var/db/pkg/ for those two. Simply delete the nvidia-kernel-* directories and portage will promptly forget it existed and leave the files as orphans. Note, ugly hack //Spider -- begin .signature This is a .signature virus! Please copy me into your .signature! See Microsoft KB Article Q265230 for more information. end pgp0.pgp Description: PGP signature
Re: [gentoo-user] emerge question
On Tuesday 02 September 2003 15:22, Philippe Van Hecke wrote: I am playing with many kernel version. And must emerge alsa-driver,nvidia-kernel for each kernel i install. My question is there is way when i emerge these two modules, to tell, with command line option to not unmerge the previous merged modules ? AUTOCLEAN=NO. Then the previous version of an ebuild will not be removed. This has to be set in the /etc/make.conf. And then you will have to be careful to clean after the packages you don't want to keep old versions of. -- Sigurd Stordal President of GOGS Experimental Petrologist -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] emerge question
I am playing with many kernel version. And must emerge alsa-driver,nvidia-kernel for each kernel i install. My question is there is way when i emerge these two modules, to tell, with command line option to not unmerge the previous merged modules ? I know that when i do emerge i have arround 5 second to tell to portage to not umerge. But i would like to have this done automaticly. I don't think that will solve your problem. Rebuilding a kernel already deletes existing modules, so emerge alsa-driver etc. is needed anyway. Gwendolyn. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge question
Thanks, for you answer. I dislike to modify my /etc/make.conf file in this way because as you say On Tuesday 02 Septyou will have you will have to be careful to clean after the packages you don't want to keep old versions of. and you can forget to remove this for other packages. So it will be cool to have the possibility to give an argument to emerge. But if there is no one i will test what you suggest. regards, Philippe. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge question
I don't think that will solve your problem. Rebuilding a kernel already deletes existing modules, so emerge alsa-driver etc. is needed anyway. Not if this a new kernel version the old kernel modules will be keep in /lib/modules/oldkernel. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge question
Philippe Van Hecke [EMAIL PROTECTED]: I am playing with many kernel version. And must emerge alsa-driver,nvidia-kernel for each kernel i install. My question is there is way when i emerge these two modules, to tell, with command line option to not unmerge the previous merged modules ? I know that when i do emerge i have arround 5 second to tell to portage to not umerge. But i would like to have this done automaticly. regards, Philippe. -- [EMAIL PROTECTED] mailing list Maybe --noreplace (-n)? I realy don't know what do you want to do, but this seams like the closest to the solution. Good luck :o) -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge question
Sigurd Stordal ([EMAIL PROTECTED]) scribbled: On Tuesday 02 September 2003 15:22, Philippe Van Hecke wrote: I am playing with many kernel version. And must emerge alsa-driver,nvidia-kernel for each kernel i install. My question is there is way when i emerge these two modules, to tell, with command line option to not unmerge the previous merged modules ? AUTOCLEAN=NO. Then the previous version of an ebuild will not be removed. This has to be set in the /etc/make.conf. And then you will have to be careful to clean after the packages you don't want to keep old versions of. Is it possible to do the following: # AUTOCLEAN=NO; emerge alsa-driver; unset AUTOCLEAN I'm having the same issue but with alsa and radeon.o Cooper. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge question
On Tuesday 02 September 2003 16:44, Philippe Van Hecke wrote: I don't think that will solve your problem. Rebuilding a kernel already deletes existing modules, so emerge alsa-driver etc. is needed anyway. Not if this a new kernel version the old kernel modules will be keep in /lib/modules/oldkernel. Not really, because same version of any package can't exist multiple times in one system. The previous incarnation is unmerged after the new is merged. One solution I could think is to add /lib/modules to CONFIG_PROTECT in ones make.conf. This prevents the removal of the module files when the previous incarnation is uninstalled. -- [EMAIL PROTECTED] mailing list
