On Thu, Jun 7, 2012 at 11:30 AM, Joan Picanyol i Puig < [email protected]> wrote:
> * Andrew Stuart <[email protected]> [20120531 16:15]: > > There are source code files and also operating system configuration > > files. > > I would keep two different repositories. For the second one, see below. > And i would go one step further and NOT use fossil for the system files. Fossil does not support file permissions other than the +x bit and does not understand user/group ownership. Without that, using it for managing system-level files is a disaster waiting to happen. If certain files do not have exactly the right permissions... kaboom. > I use sudo to edit these files as most of the files are editable only > > by root. > > > > How do I use Fossil in this context? > i strongly recommend against it. Others on this list will just as strongly argue the opposite, however. (And we're all right ;) > > Where should I set up the fossil repository? In my unprivileged user > > home directory? > The repo file itself needs to live somewhere outside of the "source tree." i tend to keep all of mine in a single dir. > > How should I be handling the need to use sudo to access the various > > files that I work on? I suspect I'll be running into various > > permissions issues constantly? > Yes. See above. If you manage to hose the rights on /etc/shadow then you could prevent users (i.e. yourself) from logging in. > Would my workflow look something like this for example? > > 1: Create fossil repo in my home directory > > 2: Go to the location of a file I want to put in fossil > > 3: "fossil open" in this directory > > 4: "fossil add" the files I wish to put under scm > That's more or less correct, but understand that all files stored in a repo must live under the same directory structure on your system. Thus you need one for /etc, one for /var/, or whatever it is you want to save. Why not just do everything from the root dir? Chicken-egg - the repo file will then live under the directory which it controls (this is considered [by myself to be] bad practice). > > Although I have read the quickstart guide it doesn't really nudge me > > in the right direction of how to actually drive it in a practical > > manner, especially where I have to use sudo. > Fossil is not the right tool for that job. (Let the flame wars begin! ;) -- ----- 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
