no ./configure file
 

I'm trying to install libpng-1.2.5 on slackware 9.1. every thing seems to be going fine until I do the ./configure. It then tells me there is no "configure" script, but that I need to choose the appropriate makefile. there is a make file "./libpng-1.2.5/scripts/makefile.linux" which I'm guessing is the one I want. The info tells me to copy the file but not where to, and to read the INSTALL file for more info.

well here are my 2 questions.
1. where and how should I copy this makefile (assuming it is the right one)?

2. how do I read the INSTALL file so that I don't have to waste ya'lls precious time with such questions?

You can read it with
vi INSTALL

Some programs don't have a configure script and use differenct programs to execute the make/install process. That's why it's always good practice to first read the INSTALL/README files.

vi suck...

pico install :D

there's a reason Pat V. did not put pico in Slackware

vi rules

dude, first of all. I don't really get vi, so therefor it SUCK! :P

and wtf? pico's in slack.. what are you thinking?

For reading text files, most is a very handy program. It's included on the Slackware disk since 9.1.
Some software has a different way of configuring. Read the docs included with the source, the answer will be there. And what tool you will use to read or edit messages that's up to you. You can choose the tool you like :)

That is merely your opinion.

Doing a seach on http://www.slackware.org/pb/
pico does not come with slackware-current or 9.1

It's not on my 9.1 either

I'm pretty sure that Pico is bundled with Dropline Gnome, this would explain the confusion going on here.

I personally usially just use cat for displaying README files. All it does is display the contents of the desired file in the console.

pico is in 9.1 it is part of the pine package.

A vote for "less INSTALL". :D

Got my vote, everyone knows that less is more - (I have to say that to all the girls :( )

Steve

Another vote for less...

and I use (g)vim for all my text editing needs... once you start on the path of the mouseless unix text editor it's very frustrating to go back... now I keep pressing escape after every time I type something. :D

Either less or most would be my recommendation if you only want to read the file. I use pico for editing (unless I'm in a GUI, when I use Gedit), but just use whatever you like best.

Off topic (since simpletoker's question seems to have been answered):

Just because you havnt taken the time to learn something doesnt mean it sucks. I used to use pico, but I found that vi is one of the most powerful editors I have come across. You should take some time out to learn the commands. There are plenty of tutorials online. Everything is done via the keyboard. There is no switching back and forth between the mouse and keyboard. It is very fast once you learn it.