1/ RedHat is a company that needs to earn money.
If static compiling is used then few people may need to buy their products.
If you read what is written, it is not said IMPOSSIBLE.
It is said DISCOURAGED, which is TOTALLY not the same.
As I said, it should be possible to dynamically linking, but I NEVER said that 
it must be possible.

What RedHat said is a commercial discuss which have nothing to do with my 
discuss.
Most people do not need a total secure software because it is not relevant in 
most software.
if it is not commercial discuss for you, then tell me why I ALWAYS compile 
static EVERY TIME it is possible with EVERY software ?
Why does fsck have a static binary ? Why do I see static binary in some 
official package ?
portableapps.org have binary that runs everywhere with windows plateform... Why 
?


2/ I do compile with static option ON when it is possible.
This is evidence that RedHat is untrue.
Is it important that the binary is less bigger, less slower at startup and so 
on ? NO.
What is important for users is that it should run everywhere.
Not in a special distro which release is X.Y.Z-i786DX.
What people need is that you just open the package every where in a folder and 
do:
./commandtorunbinary<enter>
and that's it.


3/ CVS is used by few people because in the past they forget to meet people's 
need.
SVN takes over them...
Now I do use git, because it is far better than subversion...


4/ We don't always need network support with SSL...
I can create the fossil file locally and then send my work via SSH (sFTP, 
etc.)...

 
Best Regards


K.

Stephan Beal wrote :

Why don't fossil create a lite version that could be static and the full one 
which will forbid the static option ?
>Isn't that a good idea ?

That's like asking, "why not have a fossil which has no networking support?" 
and the answer is, "because it would be nearly useless." On modern Linuxes the 
networking libraries require dynamically libraries at runtime (they will link 
but will emit a warning while linking and may or may not work at runtime).

The static limitations have NOTHING to do with fossil itself and EVERYTHING to 
do with the platform you are building it on.

Along with the other links people have provided you about this topic, i 
recommend reading:

https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Developer_Guide/lib.compatibility.static.html
(read the first sentence)

http://stackoverflow.com/questions/3430400/linux-static-linking-is-dead
(especially read the first/most highly-rated answer)

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to