Ryan,
>> (2) I'm not familiar with how UNIX software is built. Can someone
>> direct me
>> to a site that overviews it? Even better, can someone can briefly
>> explain
>> it?
>
> Briefly, no. I'd suggest one of the O'Reilly books on UNIX. Check on
> google for some O'Reilly UNIX or something, they have some of their
> books online for free. The main thing you will want to know is how
> permissions work, how the filesystem is set up, and the standard
> utilities and commands like grep, cat, cp, mkdir, chmod, etc.
Truth be told I've been using UNIX for a few years now; however, the setting
up of software, compiling, and stuff in the same genre I've left to the
SA's. Working through a CLI, setting up my environment, shell scripts, basic
Perl scripts, and things in that genre I can do.
>From a Win32 (.Net) perspective, I've got a solution with a bunch of
projects inside. I compile the solution. I deploy the application. I use the
application. I have a good (not great) understanding of how that works. This
makefile stuff I don't get. What frustrates me is every site I find simply
gives instructions on how but no explanation of why. However, DON'T answer
my question about creating UNIX software installation. I'm going to take
your advice and hit the books. Thank you for your tips though.
>> (3) Do I need to execute the statement `sudo install` as root (using
>> sudo)?
>> In the documentation sudo was not used; however, I assumed the files
>> would
>> go to a secure directory and require root privileges to be installed.
>>
>
> yes root needs to be the one installing. the sudo command runs a
> command as root. So, "sudo make install" would use the root user to
> "make install". It should ask you for the password first though. you
> would not use sudo if you were root as it would not be needed at that
> point.
Why the hell wasn't that in any of the instructions I saw! Anyway to know
what commands need to be run as root?
[...snip from DBI READ ME...]
Read the DBI README then Build/test/install the DBI by doing
perl Makefile.PL
make
make test
make install
Then delete the source directory tree since it's no longer needed.
Regards,
Adam
