Many thanks, that helped a lot!
Now I have set only those features in the PERL_FEATURES entry that were
installed before -
the warning has gone and I hoped the correct version of perl is
installed now.
Helmut
On 05/07/2024 08:29:28 PM, Jack wrote:
On 2024.05.07 12:33, Helmut Jarausch
Rich Freeman wrote:
> On Tue, May 7, 2024 at 6:04 AM Michael wrote:
>> On Tuesday, 7 May 2024 08:50:26 BST Dale wrote:
>>> I'm aware of what it is and the cable part. I was curious what it looks
>>> like to BIOS and the OS when one is connected and that pin has the drive
>>> disabled. From what
On 2024.05.07 12:33, Helmut Jarausch wrote:
Hi,
according to the NEWS from today one has to set PERL_FEATURES in
/etc/portage/make.conf.
But how to do that?
I've tried
PERL_FEATURES="debug ithreads quadmath"
but emerging dev-lang/perl-5.38.2-r3 I get
* As of dev-lang/perl-5.38.2-r3,
Hi,
according to the NEWS from today one has to set PERL_FEATURES in
/etc/portage/make.conf.
But how to do that?
I've tried
PERL_FEATURES="debug ithreads quadmath"
but emerging dev-lang/perl-5.38.2-r3 I get
* As of dev-lang/perl-5.38.2-r3, the useflags debug, ithreads,
quadmath move
On Tue, 7 May 2024 at 15:37, Neil Bothwick wrote:
> On Tue, 7 May 2024 13:22:47 +0100, Jorge Almeida wrote:
>
> > > Yes, of course. When I said "emerge -c doesn't clean it" I meant
> > > "emerge
> > -c" (without arguments). I know how to unmerge a package, which in this
> > particular case I
On Tue, 7 May 2024 13:22:47 +0100, Jorge Almeida wrote:
> > Yes, of course. When I said "emerge -c doesn't clean it" I meant
> > "emerge
> -c" (without arguments). I know how to unmerge a package, which in this
> particular case I should have done years ago, but didn't, and forgot
> about it.
On Tue, 7 May 2024 at 13:10, Neil Bothwick wrote:
> On Tue, 7 May 2024 11:32:43 +0100, Jorge Almeida wrote:
>
>
>
> Files in @world should only be wanted because you put them in there, so
> you should be able to remove them.
>
> Yes, of course. When I said "emerge -c doesn't clean it" I meant
On Tue, 7 May 2024 11:32:43 +0100, Jorge Almeida wrote:
> > > I seem to remember I installed a long time ago. It is in the world
> > > file, hence emerge -c wouldn't clean it. I don't have csh but think
> > > I had it
> >
> > emerge -c will remove packages that are in @world. It was probably
>
On Tue, May 7, 2024 at 6:04 AM Michael wrote:
>
> On Tuesday, 7 May 2024 08:50:26 BST Dale wrote:
> >
> > I'm aware of what it is and the cable part. I was curious what it looks
> > like to BIOS and the OS when one is connected and that pin has the drive
> > disabled. From what I've read in
On Tue, 7 May 2024 at 10:36, Neil Bothwick wrote:
> On Thu, 2 May 2024 16:37:24 +0100, Jorge Almeida wrote:
>
> >
> > I seem to remember I installed a long time ago. It is in the world file,
> > hence emerge -c wouldn't clean it. I don't have csh but think I had it
>
> emerge -c will remove
On Tuesday, 7 May 2024 08:50:26 BST Dale wrote:
> William Kenworthy wrote:
> > See https://www.disctech.com/powerdisable
> >
> > BillK
>
> I'm aware of what it is and the cable part. I was curious what it looks
> like to BIOS and the OS when one is connected and that pin has the drive
>
On Thu, 2 May 2024 16:37:24 +0100, Jorge Almeida wrote:
> So, it seems I have at least one package which I wouldn't expect to
> have: app-admin/xstow
>
> I seem to remember I installed a long time ago. It is in the world file,
> hence emerge -c wouldn't clean it. I don't have csh but think I had
William Kenworthy wrote:
> See https://www.disctech.com/powerdisable
>
> BillK
>
I'm aware of what it is and the cable part. I was curious what it looks
like to BIOS and the OS when one is connected and that pin has the drive
disabled. From what I've read in some places, the drive doesn't power
13 matches
Mail list logo
