> On Monday 03 April 2006 16:45, Peter Campion-Bye wrote:
>> Regarding the original problem with pilot-link, there is AFAIK no
>> way to specify FEATURES on an individual package basis (ie put
>> 'app-pda/pilot-link -sandbox' into a file named package.features,
>> in the style of the package.use fi
>
>> Regarding the original problem with pilot-link, there is AFAIK no way to
>> specify FEATURES on an individual package basis (ie put
>> 'app-pda/pilot-link -sandbox' into a file named package.features, in
>> the style of the package.use file) - is that correct?
>
> You can use /etc/portage/bash
On Mon, 3 Apr 2006 16:45:39 +0100 (BST), Peter Campion-Bye wrote:
> Regarding the original problem with pilot-link, there is AFAIK no way to
> specify FEATURES on an individual package basis (ie put
> 'app-pda/pilot-link -sandbox' into a file named package.features, in
> the style of the package.u
>
> This is resilient to the single merge between resumes case in 2.1_pre.
> For 2.0, you can manually back up and restore /var/cache/edp/mtimedb.
>
> --
> Jason Stubbs
Thanks Jason, I'll give that a try.
Regarding the original problem with pilot-link, there is AFAIK no way to
specify FEATURES on
On Monday 03 April 2006 22:12, Peter Ruskin wrote:
> On Monday 03 April 2006 13:12, Jason Stubbs wrote:
> > > I'm just experiencing the same thing - with over 800 ebuilds
> > > this is an important question. I'm noting the problem ebuilds
> > > in a log file manually, so I can see to them when it'
On Monday 03 April 2006 20:39, Peter Ruskin wrote:
> On Monday 03 April 2006 12:06, Peter Campion-Bye wrote:
> > Hi,
> > Trying to do an 'emerge -e world' I come up against the odd
> > package that doesn't build without some intervention. I know I
> > can do 'emerge --resume --skipfirst' and carry
Peter Campion-Bye wrote:
>Hi,
>Trying to do an 'emerge -e world' I come up against the odd package that
>doesn't build without some intervention. I know I can do 'emerge --resume
>--skipfirst' and carry on, but sometimes the broken package could be built ok
>with a little intervention, for example
Hi,
Trying to do an 'emerge -e world' I come up against the odd package that
doesn't build without some intervention. I know I can do 'emerge --resume
--skipfirst' and carry on, but sometimes the broken package could be built ok
with a little intervention, for example, my build breaks on pilot-link
8 matches
Mail list logo
