On 8/16/2014 04:44, Stephan Beal wrote:
Great! i've been eyeballing the Chromebook as my next PC, but it would
first of course need to be able to do fossil.
Of course, it's mainly just a Stupid Programmer Trick to use Fossil in
Chrome OS proper, since once you've got an Ubuntu/Debian chroot set up,
you'll want to use that for all command line stuff that doesn't need to
affect the Chrome OS system directly.
The source control use case is hard to sell, since getting development
tools onto the Chrome OS side is a fair bit of a pain. Then having done
so, the sandboxing rules make testing and running your program painful.
It's easier to do development inside the chroot box.
It's also hard to justify using Fossil for version control of regular
files, since Chrome OS hides your "documents" folder. It wants to
abstract everything into the cloud, via Google Drive. I happen to know
I have some PDFs synced to my local Chromebook, for example, but
sudo find / -name \*.pdf
shows nothing. The PDFs *are* there, but hidden somehow.
The only serious Fossil-on-Chrome-OS use case I can think of is the
personal wiki case.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
