Re: [gentoo-user] Different build options for specific packages
Peter Humphrey wrote: > On Saturday 11 Feb 2017 05:22:19 Dale wrote: > >> The biggest reason I needed to do this is that I usually have portage's >> work directory on tmpfs. I just don't have enough memory to do them all >> at the same time, one at a time would work tho. If I ever get around to >> upgrading to 32GBs, then this won't matter. > When your tmpfs fills up, it starts paging to swap, so as long as your swap > partition is big enough it should be about the same as using the hard disk. > I made my swap to small. Even tho I wasn't using tmpfs during a couple of the updates, I still ran out of memory. I'm not sure exactly what all was trying to emerge but I know that when the big one really got my attention, Seamonkey, Firefox, Libreoffice and several KDE type packages were in the list. Given the time it takes those to compile, I figure the big three and others were trying to compile at the same time. While just those three big ones are bad enough, whatever else was working was just way to much. Anyway, I'll update them to themselves and try to get some memory upgraded here soon. I just don't like pushing it to the point it kills other processes. Dale :-) :-)
Re: [gentoo-user] Different build options for specific packages
On Saturday 11 Feb 2017 05:22:19 Dale wrote: > The biggest reason I needed to do this is that I usually have portage's > work directory on tmpfs. I just don't have enough memory to do them all > at the same time, one at a time would work tho. If I ever get around to > upgrading to 32GBs, then this won't matter. When your tmpfs fills up, it starts paging to swap, so as long as your swap partition is big enough it should be about the same as using the hard disk. -- Regards Peter
Re: [gentoo-user] Different build options for specific packages
On Friday 10 Feb 2017 19:39:44 Dale wrote: > I generally let emerge build packages in parallel. This works because a > lot of packages are small and don't take long to build or much room > either. However, there are a few exceptions. For me, Seamonkey, > Firefox and Libreoffice cause issues. I would like those to build one > at a time instead of at the same time. I've had times where all three > have updates but having two of them at the same time occurs pretty > regular. I thought I recalled this needing to be in package.env but my > test didn't work. I put this in package.env: > > www-client/seamonkey MAKEOPTS="-j1" > www-client/firefox MAKEOPTS="-j1" > > Since I'm here, you can guess that emerge didn't like that. So, either > I'm putting that in the wrong place, the wrong way or something. Oh, I > looked at the wiki and I didn't see things like this. I just went with > what little I recalled which seems to be not correct. The way you've set it will tell portage that, when it comes to emerging seamonkey, it should only use one process(or), and likewise for firefox. I think those options will only take effect within each package, not while deciding which packages to build. What you want is some kind of interlock, so that only one of the competing packages can be emerged at a time. I don't know how to do that, sorry. > ... I may want to disable portage on tmpfs as well, for Libreoffice at > least. I've seen a description of exactly that somewhere; you need two portage tmp directories, one tmpfs and one real disk, then switch from one to the other by redefining PORTAGE_TMPDIR in package.env. Something like that, anyway. -- Regards Peter
Re: [gentoo-user] Different build options for specific packages
Neil Bothwick wrote: > On Sat, 11 Feb 2017 05:57:26 -0600, Dale wrote: > >> Neil Bothwick wrote: >>> On Sat, 11 Feb 2017 05:22:19 -0600, Dale wrote: >>> The biggest reason I needed to do this is that I usually have portage's work directory on tmpfs. I just don't have enough memory to do them all at the same time, one at a time would work tho. If I ever get around to upgrading to 32GBs, then this won't matter. >>> I get round this in another way >>> >>> % cat /etc/portage/package.env/libreoffice >>> app-office/libreoffice ccache.conf disk-tmpdir.conf >>> >>> % cat /etc/portage/env/disk-tmpdir.conf >>> PORTAGE_TMPDIR="/mnt/scratch" >>> >>> There, the larger packages use spinning rust for $TMPDIR. This not >>> only means I can merge more than one of them at once, it also means I >>> can use my computer for other things while it's happening. >>> >>> >> The last time I ummounted it from tmpfs and some of my processes were >> killed when it was done. > There's no need to unmount anything. All other packages still use the > tmpfs location, I just have the bigger ones using my hard drive. It means > I don't need to worry about things running out of space or crippling my > other use of the computer - this is on a laptop with 8GB, my desktop now > has 32GB to I let everything use tmpfs. When it ran out of ram that last time, I had everything building on disk not tmpfs. I ran out of memory because of the programs I had open and the memory needed for it to compile whatever it was it was compiling. I wasn't using memory for tmpfs at the time. It just killed some programs that were using a lot of ram instead of stopping emerge. Sort of odd now that I think about it. I'd rather it kill emerge when it runs out of ram myself. So, even with your settings, it would have done the same thing. I have no idea why it used so much ram that time. That's one reason I think it was compiling the three big ones plus some other big one or more. I think there is a couple big KDE related packages still lurking about. >> My hope was to wrestle those three under control in a way that they >> would only do one at a time without me having to monitor it or split the >> process. If I could do that, then I think the rest would be workable. >> Maybe one of the devs will add this nifty feature one day. I figure it >> will happen right after I upgrade my memory and no longer need it. >> ROFL > That would be pointless, as they would lose their most "enthusiastic" > beta tester ;-) > > Yea, well. lol Dale :-) :-)
Re: [gentoo-user] Different build options for specific packages
On Sat, 11 Feb 2017 05:57:26 -0600, Dale wrote: > Neil Bothwick wrote: > > On Sat, 11 Feb 2017 05:22:19 -0600, Dale wrote: > > > >> The biggest reason I needed to do this is that I usually have > >> portage's work directory on tmpfs. I just don't have enough memory > >> to do them all at the same time, one at a time would work tho. If I > >> ever get around to upgrading to 32GBs, then this won't matter. > > I get round this in another way > > > > % cat /etc/portage/package.env/libreoffice > > app-office/libreoffice ccache.conf disk-tmpdir.conf > > > > % cat /etc/portage/env/disk-tmpdir.conf > > PORTAGE_TMPDIR="/mnt/scratch" > > > > There, the larger packages use spinning rust for $TMPDIR. This not > > only means I can merge more than one of them at once, it also means I > > can use my computer for other things while it's happening. > > > > > > The last time I ummounted it from tmpfs and some of my processes were > killed when it was done. There's no need to unmount anything. All other packages still use the tmpfs location, I just have the bigger ones using my hard drive. It means I don't need to worry about things running out of space or crippling my other use of the computer - this is on a laptop with 8GB, my desktop now has 32GB to I let everything use tmpfs. > My hope was to wrestle those three under control in a way that they > would only do one at a time without me having to monitor it or split the > process. If I could do that, then I think the rest would be workable. > Maybe one of the devs will add this nifty feature one day. I figure it > will happen right after I upgrade my memory and no longer need it. > ROFL That would be pointless, as they would lose their most "enthusiastic" beta tester ;-) -- Neil Bothwick Math and alcohol don't mix. Don't drink and derive. pgpf33zw6XQQh.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Different build options for specific packages
Johannes Rosenberger wrote: > On 11.02.2017 12:22, Dale wrote: >> Johannes Rosenberger wrote: >>> On 11.02.2017 10:39, Dale wrote: Mick wrote: > This is how I have configured per package FEATURES here and it seems to > work. > For example configuring ccache for large packages which take days to > emerge on > an old PC: > > # cat /etc/portage/env/ccache.conf > FEATURES="ccache" > > Now I need to point particular package(s) to it: > > # cat /etc/portage/package.env > app-office/libreoffice ccache.conf > www-client/firefox ccache.conf > www-client/chromium ram_limit.conf ccache.conf > > If I want more packages to use ccache.conf I add their name/version in > the > /etc/portage/package.env file. > I just tried copying your way, except for the setting I want, and it didn't work. I'm wondering if it just won't do this particular setting for some reason. I've tried having package.env as a file and as a directory. It didn't like either way. Either it can't do this or I'm missing something really simple here. Thanks. Dale :-) :-) >>> I think the problem is that you can change FEATURES but not emerge >>> arguments while emerging since ebuild(1) is invoked fore every package >>> but emerge(1) once for all. >>> >>> So I see two possible solutions here: >>> >>> 1. Dump the list of packages to install via emerge -p. Then split the >>> list up and chain >>>emerge invocations (possibly with arg --nodeps) such that the >>> non-parallel >>>packages will be invoked separately. >>> 2. Use emerge options -j and --load-average so that no new ebuilds are >>> started >>>while one uses much cpu load. In my experience this does not >>> unparallellize >>>reliably but I am trying out to use higher job and load limits in >>> MAKEOPTS >>>than in emerge args so single packages that can utilize the whole cpu >>> do so before >>>emerge intervenes and starts another ebuild. >>> >>> I hope this helps >>> >>> Johannes >>> >>> >>> >> Based on this and Neil's reply, I may just have to tell it to exclude >> updating those when I do my regular updates. Then go back and tell it >> to do them later one at a time. >> >> The biggest reason I needed to do this is that I usually have portage's >> work directory on tmpfs. I just don't have enough memory to do them all >> at the same time, one at a time would work tho. If I ever get around to >> upgrading to 32GBs, then this won't matter. >> >> Thanks. >> >> >> Dale >> >> :-) :-) >> > What about using zram with lz4 for the work directory > (https://wiki.gentoo.org/wiki/Zram)? > Could be a good compromise. I'm using it (8GB RAM) but haven't > benchmarked against tmpfs. > > > I'll just emerge them separately until I can get some ram. Maybe then I won't need to worry about it for a while. Thanks. Dale :-) :-)
Re: [gentoo-user] Different build options for specific packages
Neil Bothwick wrote: > On Sat, 11 Feb 2017 05:22:19 -0600, Dale wrote: > >> The biggest reason I needed to do this is that I usually have portage's >> work directory on tmpfs. I just don't have enough memory to do them all >> at the same time, one at a time would work tho. If I ever get around to >> upgrading to 32GBs, then this won't matter. > I get round this in another way > > % cat /etc/portage/package.env/libreoffice > app-office/libreoffice ccache.conf disk-tmpdir.conf > > % cat /etc/portage/env/disk-tmpdir.conf > PORTAGE_TMPDIR="/mnt/scratch" > > There, the larger packages use spinning rust for $TMPDIR. This not only > means I can merge more than one of them at once, it also means I can use > my computer for other things while it's happening. > > The last time I ummounted it from tmpfs and some of my processes were killed when it was done. I had walked off so I didn't see it but I strongly suspect it ran out of memory as well. That said, I know all three, Seamonkey, Firefos and Libreoffice, were in the update list but I don't know for sure if they were the only three emerging at one time. In other words, it may have been that those three were updating plus some others as well. When I came back, Seamonkey, Firefox, a couple instances of Dolphin and a couple other programs were closed. Also, swap was maxed out. That was my biggest tip that it ran out of memory. In the past, I've seen it max out swap and then start killing other processes. My hope was to wrestle those three under control in a way that they would only do one at a time without me having to monitor it or split the process. If I could do that, then I think the rest would be workable. Maybe one of the devs will add this nifty feature one day. I figure it will happen right after I upgrade my memory and no longer need it. ROFL Thanks. Dale :-) :-)
Re: [gentoo-user] Different build options for specific packages
On Sat, 11 Feb 2017 05:22:19 -0600, Dale wrote: > The biggest reason I needed to do this is that I usually have portage's > work directory on tmpfs. I just don't have enough memory to do them all > at the same time, one at a time would work tho. If I ever get around to > upgrading to 32GBs, then this won't matter. I get round this in another way % cat /etc/portage/package.env/libreoffice app-office/libreoffice ccache.conf disk-tmpdir.conf % cat /etc/portage/env/disk-tmpdir.conf PORTAGE_TMPDIR="/mnt/scratch" There, the larger packages use spinning rust for $TMPDIR. This not only means I can merge more than one of them at once, it also means I can use my computer for other things while it's happening. -- Neil Bothwick Bury a lawyer 12 feet under, because deep down they're nice. pgpKQt9t2DfDu.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Different build options for specific packages
On 11.02.2017 12:22, Dale wrote: > Johannes Rosenberger wrote: >> On 11.02.2017 10:39, Dale wrote: >>> Mick wrote: This is how I have configured per package FEATURES here and it seems to work. For example configuring ccache for large packages which take days to emerge on an old PC: # cat /etc/portage/env/ccache.conf FEATURES="ccache" Now I need to point particular package(s) to it: # cat /etc/portage/package.env app-office/libreoffice ccache.conf www-client/firefox ccache.conf www-client/chromium ram_limit.conf ccache.conf If I want more packages to use ccache.conf I add their name/version in the /etc/portage/package.env file. >>> I just tried copying your way, except for the setting I want, and it >>> didn't work. I'm wondering if it just won't do this particular setting >>> for some reason. >>> >>> I've tried having package.env as a file and as a directory. It didn't >>> like either way. Either it can't do this or I'm missing something >>> really simple here. >>> >>> Thanks. >>> >>> Dale >>> >>> :-) :-) >>> >> I think the problem is that you can change FEATURES but not emerge >> arguments while emerging since ebuild(1) is invoked fore every package >> but emerge(1) once for all. >> >> So I see two possible solutions here: >> >> 1. Dump the list of packages to install via emerge -p. Then split the >> list up and chain >>emerge invocations (possibly with arg --nodeps) such that the >> non-parallel >>packages will be invoked separately. >> 2. Use emerge options -j and --load-average so that no new ebuilds are >> started >>while one uses much cpu load. In my experience this does not >> unparallellize >>reliably but I am trying out to use higher job and load limits in >> MAKEOPTS >>than in emerge args so single packages that can utilize the whole cpu >> do so before >>emerge intervenes and starts another ebuild. >> >> I hope this helps >> >> Johannes >> >> >> > Based on this and Neil's reply, I may just have to tell it to exclude > updating those when I do my regular updates. Then go back and tell it > to do them later one at a time. > > The biggest reason I needed to do this is that I usually have portage's > work directory on tmpfs. I just don't have enough memory to do them all > at the same time, one at a time would work tho. If I ever get around to > upgrading to 32GBs, then this won't matter. > > Thanks. > > > Dale > > :-) :-) > What about using zram with lz4 for the work directory (https://wiki.gentoo.org/wiki/Zram)? Could be a good compromise. I'm using it (8GB RAM) but haven't benchmarked against tmpfs.
Re: [gentoo-user] Different build options for specific packages
Neil Bothwick wrote: > On Fri, 10 Feb 2017 22:19:48 -0600, Dale wrote: > >> Dale wrote: >>> Howdy, >>> >>> I read where someone did this but I can't find it now. I looked at >>> the wiki and did some startpage searches, no luck. Here goes: >>> >>> I generally let emerge build packages in parallel. This works because >>> a lot of packages are small and don't take long to build or much room >>> either. However, there are a few exceptions. For me, Seamonkey, >>> Firefox and Libreoffice cause issues. I would like those to build one >>> at a time instead of at the same time. I've had times where all three >>> have updates but having two of them at the same time occurs pretty >>> regular. I thought I recalled this needing to be in package.env but >>> my test didn't work. I put this in package.env: >>> >>> www-client/seamonkey MAKEOPTS="-j1" >>> www-client/firefox MAKEOPTS="-j1" >>> >>> Since I'm here, you can guess that emerge didn't like that. So, >>> either I'm putting that in the wrong place, the wrong way or >>> something. Oh, I looked at the wiki and I didn't see things like >>> this. I just went with what little I recalled which seems to be not >>> correct. >>> >>> Can someone point me in the right direction here? Examples would be >>> nice because I may want to disable portage on tmpfs as well, for >>> Libreoffice at least. >>> >>> Thanks >>> >>> Dale >>> >>> :-) :-) >>> >> I found another howto. That ended with this setup: >> >> >> >> root@fireball / # cat /etc/portage/package.env >> www-client/seamonkey ../env/single.conf >> www-client/firefox ../env/single.conf >> >> >> root@fireball / # cat /etc/portage/env/single.conf >> MAKEOPTS="-j1" >> >> >> root@fireball / # >> >> >> From my reading, I put the setting in the env directory file and the >> package names in package.env. Thing is, it still tries to build them >> both at the same time. Once I get these two to work, I'll add >> libreoffice to it. >> >> My first test gave a error message. I added the ../env/ part and it >> doesn't give a error but it doesn't recognize it either. I'm missing >> something. My eyes ain't real good today, allergies, so I may be not >> seeing something right. > > You have done it right this time and portage is doing exactly what you > tell it to do. unfortunately that is not the same as what you want it to > do. > > MAKEOPTS governs the number of parallel processes executed by a single > compile. So your setting it is allowing parallel merges, but each one uses > only one CPU core. > > I don't think what you want can be controlled by package.env, since you > want to change an emerge command line option, not an environment > variable. What you want requires "emerge -j 1". > > That's what I was realizing. I thought I did it right the second time, actually forth time, just second that I posted. ;-) Anyway, I was just hoping that I missed some silly little something. Now to go undo what I went and done. Thanks. Dale :-) :-)
Re: [gentoo-user] Different build options for specific packages
Johannes Rosenberger wrote: > On 11.02.2017 10:39, Dale wrote: >> Mick wrote: >>> This is how I have configured per package FEATURES here and it seems to >>> work. >>> For example configuring ccache for large packages which take days to emerge >>> on >>> an old PC: >>> >>> # cat /etc/portage/env/ccache.conf >>> FEATURES="ccache" >>> >>> Now I need to point particular package(s) to it: >>> >>> # cat /etc/portage/package.env >>> app-office/libreoffice ccache.conf >>> www-client/firefox ccache.conf >>> www-client/chromium ram_limit.conf ccache.conf >>> >>> If I want more packages to use ccache.conf I add their name/version in the >>> /etc/portage/package.env file. >>> >> I just tried copying your way, except for the setting I want, and it >> didn't work. I'm wondering if it just won't do this particular setting >> for some reason. >> >> I've tried having package.env as a file and as a directory. It didn't >> like either way. Either it can't do this or I'm missing something >> really simple here. >> >> Thanks. >> >> Dale >> >> :-) :-) >> > I think the problem is that you can change FEATURES but not emerge > arguments while emerging since ebuild(1) is invoked fore every package > but emerge(1) once for all. > > So I see two possible solutions here: > > 1. Dump the list of packages to install via emerge -p. Then split the > list up and chain >emerge invocations (possibly with arg --nodeps) such that the > non-parallel >packages will be invoked separately. > 2. Use emerge options -j and --load-average so that no new ebuilds are > started >while one uses much cpu load. In my experience this does not > unparallellize >reliably but I am trying out to use higher job and load limits in > MAKEOPTS >than in emerge args so single packages that can utilize the whole cpu > do so before >emerge intervenes and starts another ebuild. > > I hope this helps > > Johannes > > > Based on this and Neil's reply, I may just have to tell it to exclude updating those when I do my regular updates. Then go back and tell it to do them later one at a time. The biggest reason I needed to do this is that I usually have portage's work directory on tmpfs. I just don't have enough memory to do them all at the same time, one at a time would work tho. If I ever get around to upgrading to 32GBs, then this won't matter. Thanks. Dale :-) :-)
Re: [gentoo-user] Different build options for specific packages
On Fri, 10 Feb 2017 22:19:48 -0600, Dale wrote: > Dale wrote: > > Howdy, > > > > I read where someone did this but I can't find it now. I looked at > > the wiki and did some startpage searches, no luck. Here goes: > > > > I generally let emerge build packages in parallel. This works because > > a lot of packages are small and don't take long to build or much room > > either. However, there are a few exceptions. For me, Seamonkey, > > Firefox and Libreoffice cause issues. I would like those to build one > > at a time instead of at the same time. I've had times where all three > > have updates but having two of them at the same time occurs pretty > > regular. I thought I recalled this needing to be in package.env but > > my test didn't work. I put this in package.env: > > > > www-client/seamonkey MAKEOPTS="-j1" > > www-client/firefox MAKEOPTS="-j1" > > > > Since I'm here, you can guess that emerge didn't like that. So, > > either I'm putting that in the wrong place, the wrong way or > > something. Oh, I looked at the wiki and I didn't see things like > > this. I just went with what little I recalled which seems to be not > > correct. > > > > Can someone point me in the right direction here? Examples would be > > nice because I may want to disable portage on tmpfs as well, for > > Libreoffice at least. > > > > Thanks > > > > Dale > > > > :-) :-) > > > > I found another howto. That ended with this setup: > > > > root@fireball / # cat /etc/portage/package.env > www-client/seamonkey ../env/single.conf > www-client/firefox ../env/single.conf > > > root@fireball / # cat /etc/portage/env/single.conf > MAKEOPTS="-j1" > > > root@fireball / # > > > From my reading, I put the setting in the env directory file and the > package names in package.env. Thing is, it still tries to build them > both at the same time. Once I get these two to work, I'll add > libreoffice to it. > > My first test gave a error message. I added the ../env/ part and it > doesn't give a error but it doesn't recognize it either. I'm missing > something. My eyes ain't real good today, allergies, so I may be not > seeing something right. You have done it right this time and portage is doing exactly what you tell it to do. unfortunately that is not the same as what you want it to do. MAKEOPTS governs the number of parallel processes executed by a single compile. So your setting it is allowing parallel merges, but each one uses only one CPU core. I don't think what you want can be controlled by package.env, since you want to change an emerge command line option, not an environment variable. What you want requires "emerge -j 1". -- Neil Bothwick WinErr 018: Unrecoverable error - System has been destroyed. Buy a new one. Old Windows licence is not valid anymore. pgpTDuibThnto.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Different build options for specific packages
On 11.02.2017 10:39, Dale wrote: > Mick wrote: >> This is how I have configured per package FEATURES here and it seems to >> work. >> For example configuring ccache for large packages which take days to emerge >> on >> an old PC: >> >> # cat /etc/portage/env/ccache.conf >> FEATURES="ccache" >> >> Now I need to point particular package(s) to it: >> >> # cat /etc/portage/package.env >> app-office/libreoffice ccache.conf >> www-client/firefox ccache.conf >> www-client/chromium ram_limit.conf ccache.conf >> >> If I want more packages to use ccache.conf I add their name/version in the >> /etc/portage/package.env file. >> > I just tried copying your way, except for the setting I want, and it > didn't work. I'm wondering if it just won't do this particular setting > for some reason. > > I've tried having package.env as a file and as a directory. It didn't > like either way. Either it can't do this or I'm missing something > really simple here. > > Thanks. > > Dale > > :-) :-) > I think the problem is that you can change FEATURES but not emerge arguments while emerging since ebuild(1) is invoked fore every package but emerge(1) once for all. So I see two possible solutions here: 1. Dump the list of packages to install via emerge -p. Then split the list up and chain emerge invocations (possibly with arg --nodeps) such that the non-parallel packages will be invoked separately. 2. Use emerge options -j and --load-average so that no new ebuilds are started while one uses much cpu load. In my experience this does not unparallellize reliably but I am trying out to use higher job and load limits in MAKEOPTS than in emerge args so single packages that can utilize the whole cpu do so before emerge intervenes and starts another ebuild. I hope this helps Johannes
Re: [gentoo-user] Different build options for specific packages
Mick wrote: > > This is how I have configured per package FEATURES here and it seems to work. > > For example configuring ccache for large packages which take days to emerge > on > an old PC: > > # cat /etc/portage/env/ccache.conf > FEATURES="ccache" > > Now I need to point particular package(s) to it: > > # cat /etc/portage/package.env > app-office/libreoffice ccache.conf > www-client/firefox ccache.conf > www-client/chromium ram_limit.conf ccache.conf > > If I want more packages to use ccache.conf I add their name/version in the > /etc/portage/package.env file. > I just tried copying your way, except for the setting I want, and it didn't work. I'm wondering if it just won't do this particular setting for some reason. I've tried having package.env as a file and as a directory. It didn't like either way. Either it can't do this or I'm missing something really simple here. Thanks. Dale :-) :-)
Re: [gentoo-user] Different build options for specific packages
On Friday 10 Feb 2017 22:19:48 Dale wrote: > Dale wrote: > > Howdy, > > > > I read where someone did this but I can't find it now. I looked at the > > wiki and did some startpage searches, no luck. Here goes: > > > > I generally let emerge build packages in parallel. This works because a > > lot of packages are small and don't take long to build or much room > > either. However, there are a few exceptions. For me, Seamonkey, > > Firefox and Libreoffice cause issues. I would like those to build one > > at a time instead of at the same time. I've had times where all three > > have updates but having two of them at the same time occurs pretty > > regular. I thought I recalled this needing to be in package.env but my > > test didn't work. I put this in package.env: > > > > www-client/seamonkey MAKEOPTS="-j1" > > www-client/firefox MAKEOPTS="-j1" > > > > Since I'm here, you can guess that emerge didn't like that. So, either > > I'm putting that in the wrong place, the wrong way or something. Oh, I > > looked at the wiki and I didn't see things like this. I just went with > > what little I recalled which seems to be not correct. > > > > Can someone point me in the right direction here? Examples would be > > nice because I may want to disable portage on tmpfs as well, for > > Libreoffice at least. > > > > Thanks > > > > Dale > > > > :-) :-) > > I found another howto. That ended with this setup: > > > > root@fireball / # cat /etc/portage/package.env > www-client/seamonkey ../env/single.conf > www-client/firefox ../env/single.conf > > > root@fireball / # cat /etc/portage/env/single.conf > MAKEOPTS="-j1" > > > root@fireball / # > > > From my reading, I put the setting in the env directory file and the > package names in package.env. Thing is, it still tries to build them > both at the same time. Once I get these two to work, I'll add > libreoffice to it. > > My first test gave a error message. I added the ../env/ part and it > doesn't give a error but it doesn't recognize it either. I'm missing > something. My eyes ain't real good today, allergies, so I may be not > seeing something right. > > Dale > > :-) :-) This is how I have configured per package FEATURES here and it seems to work. For example configuring ccache for large packages which take days to emerge on an old PC: # cat /etc/portage/env/ccache.conf FEATURES="ccache" Now I need to point particular package(s) to it: # cat /etc/portage/package.env app-office/libreoffice ccache.conf www-client/firefox ccache.conf www-client/chromium ram_limit.conf ccache.conf If I want more packages to use ccache.conf I add their name/version in the /etc/portage/package.env file. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Different build options for specific packages
wabe wrote: > Dalewrote: > >> Dale wrote: >>> Howdy, >>> >>> I read where someone did this but I can't find it now. I looked at >>> the wiki and did some startpage searches, no luck. Here goes: >>> >>> I generally let emerge build packages in parallel. This works >>> because a lot of packages are small and don't take long to build or >>> much room either. However, there are a few exceptions. For me, >>> Seamonkey, Firefox and Libreoffice cause issues. I would like >>> those to build one at a time instead of at the same time. I've had >>> times where all three have updates but having two of them at the >>> same time occurs pretty regular. I thought I recalled this needing >>> to be in package.env but my test didn't work. I put this in >>> package.env: >>> >>> www-client/seamonkey MAKEOPTS="-j1" >>> www-client/firefox MAKEOPTS="-j1" >>> >>> Since I'm here, you can guess that emerge didn't like that. So, >>> either I'm putting that in the wrong place, the wrong way or >>> something. Oh, I looked at the wiki and I didn't see things like >>> this. I just went with what little I recalled which seems to be >>> not correct. >>> >>> Can someone point me in the right direction here? Examples would be >>> nice because I may want to disable portage on tmpfs as well, for >>> Libreoffice at least. >>> >>> Thanks >>> >>> Dale >>> >>> :-) :-) >>> >> I found another howto. That ended with this setup: >> >> >> >> root@fireball / # cat /etc/portage/package.env >> www-client/seamonkey ../env/single.conf >> www-client/firefox ../env/single.conf >> >> >> root@fireball / # cat /etc/portage/env/single.conf >> MAKEOPTS="-j1" >> >> >> root@fireball / # >> >> >> >From my reading, I put the setting in the env directory file and >>> the >> package names in package.env. Thing is, it still tries to build them >> both at the same time. Once I get these two to work, I'll add >> libreoffice to it. >> >> My first test gave a error message. I added the ../env/ part and it >> doesn't give a error but it doesn't recognize it either. I'm missing >> something. My eyes ain't real good today, allergies, so I may be not >> seeing something right. > I'm not sure that I understand what you mean. Are you talking about > emerging several packages at the same time and, if so, are you sure > that -j defines how many packages are build simultaneously? > > I know that there exists a FEATURES option for make.conf called > "parallel-install". But I never used this feature or read something > about it, so all I know is that "-j" is an option for the "make" > command. It defines how many jobs are running simultaneously when > you compile a single program. > > -- > Regards > wabe > > I think you are right. I also have this setting in make.conf: EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j8 --quiet-build=n -1 --unordered-display" I think that is the -j option I want to change. I forgot about the purpose of the other one. I'm pretty sure that one is passed on to make as you said and the one I want to change is the emerge opts. I tested that change, it still didn't work but at least I'm using the right one now. Update on current settings: root@fireball / # cat /etc/portage/package.env www-client/seamonkey ../env/single.conf www-client/firefox ../env/single.conf root@fireball / # cat /etc/portage/env/single.conf EMERGE_DEFAULT_OPTS="-j1" root@fireball / # Thanks Wabe. At least it should be closer. I'm just wondering if I can still do this or not. Maybe it doesn't work that way anymore. Dale :-) :-)
Re: [gentoo-user] Different build options for specific packages
Dalewrote: > Dale wrote: > > Howdy, > > > > I read where someone did this but I can't find it now. I looked at > > the wiki and did some startpage searches, no luck. Here goes: > > > > I generally let emerge build packages in parallel. This works > > because a lot of packages are small and don't take long to build or > > much room either. However, there are a few exceptions. For me, > > Seamonkey, Firefox and Libreoffice cause issues. I would like > > those to build one at a time instead of at the same time. I've had > > times where all three have updates but having two of them at the > > same time occurs pretty regular. I thought I recalled this needing > > to be in package.env but my test didn't work. I put this in > > package.env: > > > > www-client/seamonkey MAKEOPTS="-j1" > > www-client/firefox MAKEOPTS="-j1" > > > > Since I'm here, you can guess that emerge didn't like that. So, > > either I'm putting that in the wrong place, the wrong way or > > something. Oh, I looked at the wiki and I didn't see things like > > this. I just went with what little I recalled which seems to be > > not correct. > > > > Can someone point me in the right direction here? Examples would be > > nice because I may want to disable portage on tmpfs as well, for > > Libreoffice at least. > > > > Thanks > > > > Dale > > > > :-) :-) > > > > I found another howto. That ended with this setup: > > > > root@fireball / # cat /etc/portage/package.env > www-client/seamonkey ../env/single.conf > www-client/firefox ../env/single.conf > > > root@fireball / # cat /etc/portage/env/single.conf > MAKEOPTS="-j1" > > > root@fireball / # > > > >From my reading, I put the setting in the env directory file and > >the > package names in package.env. Thing is, it still tries to build them > both at the same time. Once I get these two to work, I'll add > libreoffice to it. > > My first test gave a error message. I added the ../env/ part and it > doesn't give a error but it doesn't recognize it either. I'm missing > something. My eyes ain't real good today, allergies, so I may be not > seeing something right. I'm not sure that I understand what you mean. Are you talking about emerging several packages at the same time and, if so, are you sure that -j defines how many packages are build simultaneously? I know that there exists a FEATURES option for make.conf called "parallel-install". But I never used this feature or read something about it, so all I know is that "-j" is an option for the "make" command. It defines how many jobs are running simultaneously when you compile a single program. -- Regards wabe
Re: [gentoo-user] Different build options for specific packages
Dale wrote: > Howdy, > > I read where someone did this but I can't find it now. I looked at the > wiki and did some startpage searches, no luck. Here goes: > > I generally let emerge build packages in parallel. This works because a > lot of packages are small and don't take long to build or much room > either. However, there are a few exceptions. For me, Seamonkey, > Firefox and Libreoffice cause issues. I would like those to build one > at a time instead of at the same time. I've had times where all three > have updates but having two of them at the same time occurs pretty > regular. I thought I recalled this needing to be in package.env but my > test didn't work. I put this in package.env: > > www-client/seamonkey MAKEOPTS="-j1" > www-client/firefox MAKEOPTS="-j1" > > Since I'm here, you can guess that emerge didn't like that. So, either > I'm putting that in the wrong place, the wrong way or something. Oh, I > looked at the wiki and I didn't see things like this. I just went with > what little I recalled which seems to be not correct. > > Can someone point me in the right direction here? Examples would be > nice because I may want to disable portage on tmpfs as well, for > Libreoffice at least. > > Thanks > > Dale > > :-) :-) > I found another howto. That ended with this setup: root@fireball / # cat /etc/portage/package.env www-client/seamonkey ../env/single.conf www-client/firefox ../env/single.conf root@fireball / # cat /etc/portage/env/single.conf MAKEOPTS="-j1" root@fireball / # >From my reading, I put the setting in the env directory file and the package names in package.env. Thing is, it still tries to build them both at the same time. Once I get these two to work, I'll add libreoffice to it. My first test gave a error message. I added the ../env/ part and it doesn't give a error but it doesn't recognize it either. I'm missing something. My eyes ain't real good today, allergies, so I may be not seeing something right. Dale :-) :-)
[gentoo-user] Different build options for specific packages
Howdy, I read where someone did this but I can't find it now. I looked at the wiki and did some startpage searches, no luck. Here goes: I generally let emerge build packages in parallel. This works because a lot of packages are small and don't take long to build or much room either. However, there are a few exceptions. For me, Seamonkey, Firefox and Libreoffice cause issues. I would like those to build one at a time instead of at the same time. I've had times where all three have updates but having two of them at the same time occurs pretty regular. I thought I recalled this needing to be in package.env but my test didn't work. I put this in package.env: www-client/seamonkey MAKEOPTS="-j1" www-client/firefox MAKEOPTS="-j1" Since I'm here, you can guess that emerge didn't like that. So, either I'm putting that in the wrong place, the wrong way or something. Oh, I looked at the wiki and I didn't see things like this. I just went with what little I recalled which seems to be not correct. Can someone point me in the right direction here? Examples would be nice because I may want to disable portage on tmpfs as well, for Libreoffice at least. Thanks Dale :-) :-)