JQP wrote:
Quote
"Eugene Mayevski [SecureBlackbox]" < XXXX@XXXXX.COM >wrote in message
news:3ffdda76$ XXXX@XXXXX.COM ...
>From vendor's point of view - how can he be able to distribute
>commercial software for linux, when he needs to build against a number
>of versions of libc and other libraries used?
The Open Source answer is to distribute the source code and teach the end
user to do his own build.
JQP, please learn what you are talking about, before you say it.
I guess you have never done dynamic linking in your life!!
Do you even know what an obj file is? Guess what, it is not source code.
Have you ever done a conditional build? Do you know what Make files do?
Yes, you can use a Make file to build and link source code, but you can also
use a make to link in libraries in/to obj files and use conditional
compiles. The advantages are you are doing linking on modules and can use
conditional switches to adjust to the hardware you are compiling on.
This is a common procedure in the non MS world. Get out of an IDE sometimes.
You can do the same on Windows, with C++,or Delphi. <G>.
In addition, rpms can also be used to make a build using the conditonal make
files or they can be delivered statically linked. This too, is common.
I will certainly agree that many have, in the Linux world, not taken the
time, nor the thought, to provide adequate packaging and installation
instructions, but that has and is changing.
So, suppose that I send a make file or a rpm src file and ask the user to
do it themselves. This is not a common practice to those outside of the
Unix, AS400, or OS390 world, agreed, but all that you would have to teach
an end user is to type in make <filename>, or rpm -ivh <filename>. I guess
that might be too hard for some people <G>.
However, I am amazed that you feel that a user should not have to go to a
terminal and type "make" or rpm -ivh to install an application, but they
should be able to run a Windows install program and answer all sorts of
questions (where is the drive, what is installed, click here, click there,
etc). So which is really more difficult, typing make <fileName>, or going
to Windows explorer and finding an icon, clicking on that icon, and
answering questions? Seems to me that one is not more difficult than the
other.
To make it short and sweet, if you can install Windows or a Windows program,
then you can install 90% of Linux open source programs that are in release
state, and any modern Linux distro itself (like Mandrake or Suse). Roll
your own Linux distros (like Slackware, Debian Woody, Gentto, etc.) are not
made for the faint of heart, nor the Linux newbie, but they are not
designed to be. If you want to build your system from the ground up, use a
Slack, Gentoo, or Debian sources. You can make it as lean and mean as you
desire. At least you have a choice between ease of use or a speed demon.
What choice do you have with Windows? What they build and sell, is the only
choice you have.
Another great thing about Linux is, that you can upgrade the core of the OS,
without having to do a fresh install of everything. Try that with Windows.