On Fri, Mar 13, 2015 at 4:22 PM, Graeme Pietersz <[email protected]> wrote:
> 6. There are cases where Fossil’s single-executable philosophy really >> matters. The ones I’ve run into amounted to cross-compiling: it’s easier >> to build an ARM executable for a Chromebook or Raspberry Pi and copy just >> that across than to set up a whole cross-compilation toolchain complete >> with shared libraries, package managers, etc., then ship some massive >> bolus-of-code over to the other platform and unpack it there. You don’t >> always get the luxury of building on the target platform. ChromeOS doesn’t >> even come with compilers. >> > In the case of the Pi, Git and Fossil (and Mercurial and Bazaar and more) > are in the Raspbian repos. So is gcc so I imagine you could compile the > latest version on the Pi itself if you wanted to. > > ChromeOS seems to be rather an odd choice for a development machine, and > if you are not using it for development why would you want to install a > DVCS on it? Is this really a common problem? I can appreciate (potentially, anyway) why one might want fossil on a ChromeOS machine, given the ability to do wiki & ticket stuff via the web interface. One could do all that stuff while disconnected even if actual code banging was not in progress. -- Scott Robison
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
