Re: [fossil-users] Newbie question - how to raise a ticket at https://www.fossil-scm.org/
On 2/25/15, Marcus Lam marcus...@outlook.com wrote: Noted. On the Fossil Concepts page, under section 4.2 Manual-Merge Workflow, at step 8 there is a typo of use use. Thanks. Should be fixed now. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question - how to raise a ticket at https://www.fossil-scm.org/
Noted. On the Fossil Concepts page, under section 4.2 Manual-Merge Workflow, at step 8 there is a typo of use use. Regards Marcus Lam Date: Wed, 25 Feb 2015 00:12:36 -0500 From: d...@sqlite.org To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Newbie question - how to raise a ticket at https://www.fossil-scm.org/ On 2/25/15, Marcus Lam marcus...@outlook.com wrote: Hi, New to Fossil. Found a typo while reading the online Fossil Concepts page. Want to raise a ticket for that but could not locate instruction for doing so. Any pointer? Email to this mailing list is the fastest way to get something fixed. -- D. Richard Hipp d...@sqlite.org ___ 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
Re: [fossil-users] Newbie question - how to raise a ticket at https://www.fossil-scm.org/
On 2/25/15, Marcus Lam marcus...@outlook.com wrote: Hi, New to Fossil. Found a typo while reading the online Fossil Concepts page. Want to raise a ticket for that but could not locate instruction for doing so. Any pointer? Email to this mailing list is the fastest way to get something fixed. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Newbie question - how to raise a ticket at https://www.fossil-scm.org/
Hi, New to Fossil. Found a typo while reading the online Fossil Concepts page. Want to raise a ticket for that but could not locate instruction for doing so. Any pointer? Regards Marcus Lam ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question
I use Unix, so I use symlinks for this, but an alternative is to have multiple checkouts of the same repo nested inside the other repos, sort of like: Assume ~/Fossil/lin.fossil, ~/Fossil/proj0.fossil ~/Fossil/proj1.fossil mkdir proj0 proj1 cd proj0 fossil open ~/Fossil/proj0.fossil mkdir lib cd lib fossil open --nested ~/Fossil/lib.fossil cd .. cd proj1 fossil open ~/Fossil/proj1.fossil mkdir lib cd lib fossil open --nested ~/Fossil/lib.fossil The only trick being that you have to remember to commit/update when you make changes. ../Dave ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question
On Fri, Nov 7, 2014 at 4:42 PM, David Mason dma...@ryerson.ca wrote: The only trick being that you have to remember to commit/update when you make changes. fossil all changes can show you which ones have edits. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question
Sweet! - Original Message - From: Stephan Beal To: Fossil SCM user's discussion Sent: Friday, November 07, 2014 10:52 AM Subject: Re: [fossil-users] Newbie question On Fri, Nov 7, 2014 at 4:42 PM, David Mason dma...@ryerson.ca wrote: The only trick being that you have to remember to commit/update when you make changes. fossil all changes can show you which ones have edits. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf -- ___ 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
Re: [fossil-users] Newbie question
David Mason wrote... I use Unix, so I use symlinks for this, but an alternative is to have multiple checkouts of the same repo nested inside the other repos, sort of like: Assume ~/Fossil/lin.fossil, ~/Fossil/proj0.fossil ~/Fossil/proj1.fossil mkdir proj0 proj1 cd proj0 fossil open ~/Fossil/proj0.fossil mkdir lib cd lib fossil open --nested ~/Fossil/lib.fossil cd .. cd proj1 fossil open ~/Fossil/proj1.fossil mkdir lib cd lib fossil open --nested ~/Fossil/lib.fossil The only trick being that you have to remember to commit/update when you make changes. Thanks, Dave. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question
Tony Papadimitriou wrote... The way I solve this problem is to keep a repo of all projects that share the same libraries together. This creates some other minor problems (that were recently made less of a problem with the -p option enhancement of the TIMELINE command.) But, I think this is the only reasonable way. There is also another possibility. Under Windows, you can use the MKLINK command to create a directory junction under your project (each project). This way you can keep the tree structure you have, keep a single copy of your libraries, but make it appear as if each project has its own copy. FOSSIL will treat this as a normal directory, meaning that if you open the repo somewhere else (where the junction does not exist), you will get a copy of you library. One potential problem with this approach is that, even though there is a single copy of the library, each project thinks it has a private copy. So, making library changes for the sake of one project have to be propagates to all other repos using the same library in their projects. Tony Thanks, Tony. -Original Message- From: jose isaias cabrera Sent: Friday, November 07, 2014 12:32 AM To: fossil-users@lists.fossil-scm.org Subject: [fossil-users] Newbie question Greetings! First of all, I want to thank you whomever was the creator of this wonderful utility. Props to you. I have a setup on my Windows PC where I have many sources of various languages. That will be another question later, but today, I have a project, which I created a repo for it, but I have libraries somewhere else. Imagine this scenario: Project lives on: c:\sources\d\MyProject\MyProject.d Libraries used by this project live on: c:\D\import \my\lib\aaa.d \my\lib\bbb.d \my\lib\ccc.d \my\lib\ddd.d \my\lib\eee.d \my\lib\fff.d \other0\lib\aaa.d \other1\lib\aaa.d The problem is that when I make changes to the to the c:\sources\d\MyProject\MyProject.d everything is fine I get the new version etc. But, when I make changes in c:\D\Import, the changes are not being checked in. I know I can open another repo and keep track of them like that, but is there another way where I can point to another directory and still use the repo for c:\sources\d\MyProject\MyProject.d? I hope I was clear enough. Thanks. josé ___ 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question
On Fri, Nov 7, 2014 at 2:42 AM, Tony Papadimitriou to...@acm.org wrote: There is also another possibility. Under Windows, you can use the MKLINK command to create a directory junction under your project (each project). This way you can keep the tree structure you have, keep a single copy of your libraries, but make it appear as if each project has its own copy. FOSSIL will treat this as a normal directory, meaning that if you open the repo somewhere else (where the junction does not exist), you will get a copy of you library. One potential problem with this approach is that, even though there is a single copy of the library, each project thinks it has a private copy. So, making library changes for the sake of one project have to be propagates to all other repos using the same library in their projects. Fossil supports nested checkouts. Maybe if the link/directory junction pointed to a checkout of the shared library, Fossil will behave as though the library checkout was an actual nested checkout. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Newbie question
Greetings! First of all, I want to thank you whomever was the creator of this wonderful utility. Props to you. I have a setup on my Windows PC where I have many sources of various languages. That will be another question later, but today, I have a project, which I created a repo for it, but I have libraries somewhere else. Imagine this scenario: Project lives on: c:\sources\d\MyProject\MyProject.d Libraries used by this project live on: c:\D\import \my\lib\aaa.d \my\lib\bbb.d \my\lib\ccc.d \my\lib\ddd.d \my\lib\eee.d \my\lib\fff.d \other0\lib\aaa.d \other1\lib\aaa.d The problem is that when I make changes to the to the c:\sources\d\MyProject\MyProject.d everything is fine I get the new version etc. But, when I make changes in c:\D\Import, the changes are not being checked in. I know I can open another repo and keep track of them like that, but is there another way where I can point to another directory and still use the repo for c:\sources\d\MyProject\MyProject.d? I hope I was clear enough. Thanks. josé ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question
On 11/6/14, jose isaias cabrera jic...@cinops.xerox.com wrote: Greetings! First of all, I want to thank you whomever was the creator of this wonderful utility. Props to you. That'd be drh (Richard Hipp) and a collection of contributors. I have a setup on my Windows PC where I have many sources of various languages. That will be another question later, but today, I have a project, which I created a repo for it, but I have libraries somewhere else. Imagine this scenario: Project lives on: c:\sources\d\MyProject\MyProject.d Libraries used by this project live on: c:\D\import \my\lib\aaa.d \my\lib\bbb.d \my\lib\ccc.d \my\lib\ddd.d \my\lib\eee.d \my\lib\fff.d \other0\lib\aaa.d \other1\lib\aaa.d The problem is that when I make changes to the to the c:\sources\d\MyProject\MyProject.d everything is fine I get the new version etc. Yes, because those files are in the repositorys working directory... But, when I make changes in c:\D\Import, the changes are not being checked in. Because these are not known to the repository, and are definitely outside the scope of it's working directory hierarchy. I know I can open another repo and keep track of them like that, but is there another way where I can point to another directory and still use the repo for c:\sources\d\MyProject\MyProject.d? You need to get that ./D/* under the umbrella of the top-level of your working directory. You could move it there, and run it from there. That could be problematic if that lib/code is shared among people or projects. If you don't _move_ it there, you could make copies of it. Obviously storing this code twice will increase your storage requirements (although, as I type this, if you're using a filesystem like ZFS w/ de-dupe capabilities, this might not necessarily be true, but I digress...). I do this (copying code) for projects of mine that depend on third party libraries... when a release of the third-party code is released, I'll update my local copy too. This is nice for a couple reasons: 1) You build against code you know (ie: your project-local copy) 2) You have that code in your repo -- so in the future if you can't find libxyz-1.1.9 from the vendor, you might have your own copy of what you care about 3) Having the code in-scope as far as a project goes means it's simple(r) to browse it's functions, #defines, etc during the course of your development. I hope I was clear enough. Thanks. Hope I understood clearly, and this helps. -bch josé ___ 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
Re: [fossil-users] Newbie question
B Harder wrote... On 11/6/14, jose isaias cabrera jic...@cinops.xerox.com wrote: Greetings! First of all, I want to thank you whomever was the creator of this wonderful utility. Props to you. That'd be drh (Richard Hipp) and a collection of contributors. Wow! Dr. Hipp is just full of goodies. :-) You need to get that ./D/* under the umbrella of the top-level of your working directory. You could move it there, and run it from there. Thanks. I hope I was clear enough. Thanks. Hope I understood clearly, and this helps. thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question
The way I solve this problem is to keep a repo of all projects that share the same libraries together. This creates some other minor problems (that were recently made less of a problem with the -p option enhancement of the TIMELINE command.) But, I think this is the only reasonable way. There is also another possibility. Under Windows, you can use the MKLINK command to create a directory junction under your project (each project). This way you can keep the tree structure you have, keep a single copy of your libraries, but make it appear as if each project has its own copy. FOSSIL will treat this as a normal directory, meaning that if you open the repo somewhere else (where the junction does not exist), you will get a copy of you library. One potential problem with this approach is that, even though there is a single copy of the library, each project thinks it has a private copy. So, making library changes for the sake of one project have to be propagates to all other repos using the same library in their projects. Tony -Original Message- From: jose isaias cabrera Sent: Friday, November 07, 2014 12:32 AM To: fossil-users@lists.fossil-scm.org Subject: [fossil-users] Newbie question Greetings! First of all, I want to thank you whomever was the creator of this wonderful utility. Props to you. I have a setup on my Windows PC where I have many sources of various languages. That will be another question later, but today, I have a project, which I created a repo for it, but I have libraries somewhere else. Imagine this scenario: Project lives on: c:\sources\d\MyProject\MyProject.d Libraries used by this project live on: c:\D\import \my\lib\aaa.d \my\lib\bbb.d \my\lib\ccc.d \my\lib\ddd.d \my\lib\eee.d \my\lib\fff.d \other0\lib\aaa.d \other1\lib\aaa.d The problem is that when I make changes to the to the c:\sources\d\MyProject\MyProject.d everything is fine I get the new version etc. But, when I make changes in c:\D\Import, the changes are not being checked in. I know I can open another repo and keep track of them like that, but is there another way where I can point to another directory and still use the repo for c:\sources\d\MyProject\MyProject.d? I hope I was clear enough. Thanks. josé ___ 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
Re: [fossil-users] Newbie question about basics of using fossil
On Thu, Jun 7, 2012 at 11:30 AM, Joan Picanyol i Puig lists-fos...@biaix.org wrote: * Andrew Stuart andrew.stu...@supercoders.com.au [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 fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question about basics of using fossil
Le 2012-06-07 à 05:30, Joan Picanyol i Puig lists-fos...@biaix.org a écrit :
* Andrew Stuart andrew.stu...@supercoders.com.au [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.
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?
Where should I set up the fossil repository? In my unprivileged user
home directory?
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?
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
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.
This has come up before. See
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg04760.html
What I'm currently doing is have soft-link to / in the directory of
a non-root admin user. I don't know if/how it interacts with symlinks
support. The versions of fossil in which I have this setup are:
This is fossil version 1.21 [002580c50d] 2011-12-13 13:53:56 UTC
This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC
I'm still hoping for improved handling of permissions, and have not yet
explored the possibilities of Add the ability to run TH1 scripts after
sync requests
Needless to say, I'd encourage you to share your findings for the
fossil as a SCM for OS configuration use case.
For file from '/': look this thread:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05576.html
Fossil isn't usable from '/' dir. as a checkout. Some commands sometimes work,
most of them doesn't. So for system config. I end up working on a checkout
somewhere in a subdir in my home and I have a script which copy file that have
changed from '/' to my checkout. ('fossil ls' is useful here)
So I always edit files from '/', and after I sync to my checkout dir with the
script. I would like very much to work directly where file are used, I might
try to start a branch to fix that eventually.
--
Martin G.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question about basics of using fossil
On Thu, Jun 7, 2012 at 6:11 AM, Stephan Beal sgb...@googlemail.com wrote: On Thu, Jun 7, 2012 at 11:30 AM, Joan Picanyol i Puig lists-fos...@biaix.org wrote: * Andrew Stuart andrew.stu...@supercoders.com.au [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! ;) In my use case, I only use it in one direction. It's only to have a nice history of what change in system files. I would not do a checkout with a specific revision or anything else that would alter files in system config using a fossil command.. for sure it would be nice to keep permission and ownership may be storing the output of: ls -ln $(fossil ls) in the repo could be used from a script to check/restore permissions... -- Martin G. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question about basics of using fossil
On Thu, Jun 7, 2012 at 12:38 PM, Martin Gagnon eme...@gmail.com wrote: sure it would be nice to keep permission and ownership may be storing the output of: ls -ln $(fossil ls) in the repo could be used from a script to check/restore permissions... Permissions are a touchy subject because they're inherently platform-specific and fossil tries to be platform-agnostic insofar as is feasible. Once fossil has Unix permissions support, people will want extended attributes support, ACLs, and other weird stuff (not that Unix permissions aren't weird, but they are the most common case). Fossil initially had _no_ support for permission, on portability/philosophical grounds, but Richard eventually caved to public pressure and added support for the executable bit primarily because not having it breaks the configure script which lives in the vast majority of open source repos. Fossil is designed/meant for managing _source repos_, and it is very rare that source repos use non-default permissions for files (other than +x, which is an unfortunate but exceedingly common special case). -- - 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
Re: [fossil-users] Newbie question about basics of using fossil
On Thu, Jun 7, 2012 at 1:36 PM, Stephan Beal sgb...@googlemail.com wrote: and fossil tries to be platform-agnostic insofar as is feasible. Once fossil has Unix permissions support, people will want extended attributes support, ACLs, and other weird stuff (not that Unix permissions aren't weird, but they are the most common case). What might be possible within the current code base would be something similar to svn properties. i think tags (which are key/value pairs in fossil) could be used for this if we would extend them to be able to tag arbitrary artifact types (i seem to recall, possibly incorrectly, that we can only tag commits right now?). e.g. tag unix-perms=0754. That might even have other interesting uses (specifying the mime type comes to mind (fossil's current support for mime types is quite minimal)) and abuses (nothing comes to mind, but i have no gift for spotting malicious abuses and attack vectors). When/if tcl scripting ever becomes a core fossil feature, a post-checkout/post-revert script could then check/set permissions based on the tags. Anyway... -- - 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
Re: [fossil-users] Newbie question about basics of using fossil
At Thu, 7 Jun 2012 12:11:00 +0200, Stephan Beal wrote: 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 ;) I personally use fossil for (among other things), managing my /etc directory on two different machines. Thus far, I've had no problems, although I took care to ensure that certain offending files were not included. I manage the repository as root, make sure that all permissions remain root only, with no group access, and made the web interface permissions never allow nobody/anonymous (there were other details that I paid attention to, security-wise, as well). That said, I primarily just use it to revert or backup certain files when they change unexpectedly. I don't think that managing the '/' directory under fossil seems like a great idea, but I've been wrong before. :) Tim ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question about basics of using fossil
[attempting to regroup subthreads]
[if short on time, please skim to the end to comment on the design]
* Martin Gagnon eme...@gmail.com [20120607 12:06]:
Le 2012-06-07 à 05:30, Joan Picanyol i Puig lists-fos...@biaix.org a écrit :
* Andrew Stuart andrew.stu...@supercoders.com.au [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.
I use sudo to edit these files as most of the files are editable only
by root.
[...]
Needless to say, I'd encourage you to share your findings for the
fossil as a SCM for OS configuration use case.
For file from '/': look this thread:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05576.html
Fossil isn't usable from '/' dir. as a checkout. Some commands
sometimes work, most of them doesn't. So for system config. I end up
working on a checkout somewhere in a subdir in my home and I have a
script which copy file that have changed from '/' to my checkout.
('fossil ls' is useful here)
I did save your message from that thread, but ruby meld are
incompatible with my minimal depencies policy. Also, sudo does have
its own issues and is not available in several scenarios.
* Stephan Beal sgb...@googlemail.com [20120607 12:04]:
On Thu, Jun 7, 2012 at 11:30 AM, Joan Picanyol i Puig
lists-fos...@biaix.org wrote:
* Andrew Stuart andrew.stu...@supercoders.com.au [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.
I would consider being able to use fossil for this a step further :)
Fossil does not support file permissions other than the +x bit
But this can be just a missing feature, from
http://www.fossil-scm.org/fossil/doc/trunk/www/fileformat.wiki :
The optional 3rd argument defines any special access permissions
associated with the file. The only special code currently defined is
x which means that the file is executable. All files are always
readable and writable.
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.
pre-commit/post-update hooks could be used to work around this issue.
See below regarding your use tags for tracking permissions proposal.
The repo file itself needs to live somewhere outside of the source tree.
I'm not convinced this is true, in fact I believe I've had the repo at
the root of the checkout some times.
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).
fossil will ignore the repo file if you don't add it.
Fossil is not the right tool for that job.
I'd certainly like it to be.
* Martin Gagnon eme...@gmail.com [20120607 12:32]:
may be storing the output of: ls -ln $(fossil ls) in the
repo could be used from a script to check/restore permissions...
uids (or SIDs in Windows) might not be constant among diferents systems.
I believe the uid-uname mapping should be preserved on commit and
require a command line override if it differs on checkout
* Stephan Beal sgb...@googlemail.com [20120607 13:29]:
Permissions are a touchy subject because they're inherently
platform-specific and fossil tries to be platform-agnostic insofar as is
feasible. Once fossil has Unix permissions support, people will want
extended attributes support, ACLs, and other weird stuff (not that Unix
permissions aren't weird, but they are the most common case).
I believe the (basic) Unix permission model can be easily supported in
post-NT-Windows.
* Stephan Beal sgb...@googlemail.com [20120607 13:38]:
i think tags (which are key/value pairs in fossil) could be used for
this if we would extend them to be able to tag arbitrary artifact
types (i seem to recall, possibly incorrectly, that we can only tag
commits right now?). e.g. tag unix-perms=0754.
That could be a good idea, but the file format does not seem to be
easily extended to support tagging File cards, since Tags are a card
in the manifest as well. I believe it is much easier to extend de File
card specification in a backward compatible way by specifying a 3 digit
special code to mean this permissions as defined by chmod(). Extend it
still further to preserve uid-login.
qvb
--
pica
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question about basics of using fossil
On Fri, Jun 8, 2012 at 1:10 AM, Joan Picanyol i Puig lists-fos...@biaix.org wrote: The repo file itself needs to live somewhere outside of the source tree. I'm not convinced this is true, in fact I believe I've had the repo at the root of the checkout some times. Sorry, i was thinking of another case: trying to open a repo from within another repo. IIRC fossil fails by default if you do this but allows a flag override that (i may be wrong about the flag). 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). fossil will ignore the repo file if you don't add it. In the general case it's bad practice to keep the repo in the directory being controlled. Too many things can go wrong. e.g. i once did a global find/grep/replace in a source tree and, due to a broken glob, ended up corrupting my repo file. (i've done similar things to svn checkouts more than once, hosing the .svn directory state.) I believe the (basic) Unix permission model can be easily supported in post-NT-Windows. i'm willing to bet that if sufficient[ly portable] patches were contributed, Richard would bless them. That could be a good idea, but the file format does not seem to be easily extended to support tagging File cards, since Tags are a card in the manifest as well. I believe it is much easier to extend de File card specification in a backward compatible way by specifying a 3 digit special code to mean this permissions as defined by chmod(). Extend it still further to preserve uid-login. i have no idea - i'm not familiar with the raw manifest format. -- - 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] Newbie question about basics of using fossil
Hello all, I'm a complete newb with fossil and trying to grasp some basic concepts. I have an Ubuntu system that I am developing on. I want to ensure that various files that I modify are in Fossil SCM. There are source code files and also operating system configuration files. 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? Where should I set up the fossil repository? In my unprivileged user home directory? 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? 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 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. thanks heaps. Andrew ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question about basics of using fossil
On Thu, May 31, 2012 at 7:21 AM, Andrew Stuart andrew.stu...@supercoders.com.au wrote: Hello all, I'm a complete newb with fossil and trying to grasp some basic concepts. I have an Ubuntu system that I am developing on. I want to ensure that various files that I modify are in Fossil SCM. There are source code files and also operating system configuration files. 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? Where should I set up the fossil repository? In my unprivileged user home directory? 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? 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 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. From your email I gather that you have a mix of files to control, some are perhaps in /etc or some other system location and some are source files? Your recipe above would work if *all* the files to be controlled live under the location where you ran the fossil open command. However I suggest not attempting to directly control the system files. Instead copy the files to a working area where you do the fossil open then write a Makefile that has rules to put the files in place. E.g. something like this: /etc/some/file.cfg : file.cfg sudo install file.cfg /etc/some/file.cfg thanks heaps. Andrew __**_ fossil-users mailing list fossil-users@lists.fossil-scm.**org fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-usershttp://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
[fossil-users] newbie question - no answer in the wiki
Hello there, Sorry for the newbie question but I have lived without scm all my life and am just getting into fossil, as I am about to become a part of a larger development project. bjorn@box:~/Desktop/fossil-test$ fossil checkout testrepo fossil: there are unsaved changes in the current checkout bjorn@box:~/Desktop/fossil-test$ fossil commit fossil: missing file: dyr.jpg fossil: aborting due to prior errors Can somebody translate this error message into a solution? Cheers, BM ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] newbie question - no answer in the wiki
On Fri, Feb 17, 2012 at 11:51 AM, Bjorn Madsen bjorn.mad...@operationsresearchgroup.com wrote: bjorn@box:~/Desktop/fossil-test$ fossil checkout testrepo fossil: there are unsaved changes in the current checkout bjorn@box:~/Desktop/fossil-test$ fossil commit fossil: missing file: dyr.jpg fossil: aborting due to prior errors Can somebody translate this error message into a solution? 'fossil status' will probably show you that dyr.jpg is missing - it was added to the repo at some point but the local copy is not there. You can get back the most recent copy (assuming it was ever checked in before) with: fossil revert dyr.jpg If it was never checked in before then you'll need to create/recover dyr.jpg (or fossil rm dyr.jpg, i think) before committing. i hope that helps, -- - 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
Re: [fossil-users] newbie question - no answer in the wiki
Excellent - thank you! On 17 February 2012 11:22, Richard Hipp d...@sqlite.org wrote: On Fri, Feb 17, 2012 at 5:51 AM, Bjorn Madsen bjorn.mad...@operationsresearchgroup.com wrote: Hello there, Sorry for the newbie question but I have lived without scm all my life and am just getting into fossil, as I am about to become a part of a larger development project. bjorn@box:~/Desktop/fossil-test$ fossil checkout testrepo fossil: there are unsaved changes in the current checkout bjorn@box:~/Desktop/fossil-test$ fossil commit fossil: missing file: dyr.jpg fossil: aborting due to prior errors Can somebody translate this error message into a solution? You have done fossil add dyr.jpg at some point, but no file named dyr.jpg exists in your checkout. Either create the file, or do fossil rm dyr.jpg before you commit. Cheers, BM ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Bjorn Madsen *Researcher Complex Systems Research* Ph.: (+44) 0 7792 030 720 Ph.2: (+44) 0 1767 220 828 bjorn.mad...@operationsresearchgroup.com ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question : how to find new files/dirs in working dir ?
Hi, Think Niht wrote: Hello, I am new to fossil. Is there a way to find which files/dirs which have been added to working tree and unknown to fossil ? I think it's called: fossil extra Thanks. TNT. -- Regards, Hakki Dogusan ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Newbie question : how to find new files/dirs in working dir ?
Seems to be what I was asking for! Thanks a lot. TNT. On Tue, Aug 11, 2009 at 1:44 AM, Hakki Dogusan dogus...@tr.net wrote: Hi, Think Niht wrote: Hello, I am new to fossil. Is there a way to find which files/dirs which have been added to working tree and unknown to fossil ? I think it's called: fossil extra Thanks. TNT. -- Regards, Hakki Dogusan ___ 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
