Re: [Cooker] ncurses-devel no version matching current ncurses package!

2001-03-29 Thread Ryan Little


- Original Message -
From: "Spencer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 29, 2001 11:26 PM
Subject: Re: [Cooker] ncurses-devel no version matching current ncurses
package!


> On March 29, 2001 07:41 pm, you wrote:
> > The newest ncurses package is ncurses-5.2-12mdk-src.rpm
> > unfortunatley no one has built an ncurses-devel package to match, you
can
> > install ncurses-devel-5.1-8mdk-i586.rpm with --nodeps and it appears to
> > work fine, but it's no fun getting the dependency problem, maybe instead
of
> > ncurses-devel-5.1-8mdk-i586.rpm requiring =5.2-12 we could throw a >= in
> > there ? unless someone is working on a new devel package, which would be
> > even better :)
> > Ryan
>
> Try libncurses5, libncurses5-devel
> ---
> Spence
Ahh nothing like a change in the naming convention to throw a fella off :P
Thanks
Ryan





Re: [Cooker] ncurses-devel no version matching current ncurses package!

2001-03-29 Thread Spencer

On March 29, 2001 07:41 pm, you wrote:
> The newest ncurses package is ncurses-5.2-12mdk-src.rpm
> unfortunatley no one has built an ncurses-devel package to match, you can
> install ncurses-devel-5.1-8mdk-i586.rpm with --nodeps and it appears to
> work fine, but it's no fun getting the dependency problem, maybe instead of
> ncurses-devel-5.1-8mdk-i586.rpm requiring =5.2-12 we could throw a >= in
> there ? unless someone is working on a new devel package, which would be
> even better :)
> Ryan

Try libncurses5, libncurses5-devel
---
Spence




[Cooker] ncurses-devel no version matching current ncurses package!

2001-03-29 Thread Ryan Little

The newest ncurses package is ncurses-5.2-12mdk-src.rpm
unfortunatley no one has built an ncurses-devel package to match, you can
install ncurses-devel-5.1-8mdk-i586.rpm with --nodeps and it appears to work
fine, but it's no fun getting the dependency problem, maybe instead of
ncurses-devel-5.1-8mdk-i586.rpm requiring =5.2-12 we could throw a >= in
there ? unless someone is working on a new devel package, which would be
even better :)
Ryan