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
>
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 th
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
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
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 sa
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 wh
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
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
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
>>
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
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/e
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
> >
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"
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
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
> > lo
wabe wrote:
> 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 a
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
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
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, t
19 matches
Mail list logo
