> > I'm not sure if I understand what's being said, but if I do, I would > disagree that Fossil sans networking support would be "nearly useless". > > I use Fossil locally exclusively. I may be in the minority. I do not know. >
"Nearly" meaning essentially "for everyone who uses it with remote repos AND everyone who uses the built-in UI," which covers the vast majority of users. Since the whole UI is an HTML interface, networking is more or less implied. Without the networking support "fossil server" and "fossil ui" could not work. The issue of static linking is not an app-level problem, it's an environment-level problem. Fossil aims to be as platform-neutral as possible and, like the C standard itself, does not address the minutia of platform-specific quirks like dynamic vs static linking. i apologize if i seem a bit riled up/annoyed about this, but the OP keeps asking (trolling, it seems!) again and again, despite being given plentiful information and links where he can follow up on it, "why can't I build this statically?" The answer (again) is "you _can_, but on Linux, Solaris 10/OpenSolaris, and possibly other platforms, you _will_ run into platform-level limitations which we cannot fix at the application level." -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
