Fossil and Filetree
Locked
123
123
 
|
Hi,
I have been trying Fossil with Filetree, and I was rather please by the mutuals use of these tools. So I may share a few feedbacks. Fossil[1] itself is a software to manage source code development. It is very simple to install and data is saved in a single sqlite database. It comes with source code management, bug tracker, web interface, wiki and timeline tools. I was a bit afraid by the filetree atomic commit (one file per method) to manage it without much headache with file based VCS. However fossil comes with a nice command: 'fossil addremove' to add/remove the changed files in the repo. So it went fine. So all in all, it is pretty nice if one want to move to a private souce code management system with very little requirement. Hilaire [1] http://www.fossil-scm.org -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
|
2015-10-20 11:09 GMT+02:00 Hilaire <[hidden email]>: Hi, I was a bit afraid by the filetree atomic commit (one file per method) So it looks very similar to a filetree + git workflow ? Any taker on adding a fossil interface to filetree with the same approach as GitFileTree ? Thierry
|
|
|
Le 20/10/2015 11:20, Thierry Goubier a écrit :
> So it looks very similar to a filetree + git workflow ? I don't know much git, but I guess it will the same > > Any taker on adding a fossil interface to filetree with the same > approach as GitFileTree ? I will take a look, adapting should be quite simple I guess. Hilaire > > Thierry -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
|
|
In reply to this post by Thierry Goubier
Le 20/10/2015 11:20, Thierry Goubier a écrit :
> So it looks very similar to a filetree + git workflow ? > > Any taker on adding a fossil interface to filetree with the same > approach as GitFileTree ? > > Thierry Which version of GitFileTree should I take for Pharo3? Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
|
|
2015-10-20 12:13 GMT+02:00 Hilaire <[hidden email]>: Le 20/10/2015 11:20, Thierry Goubier a écrit : Hum, let me check what is the condition of this one. Thierry
|
|
|
2015-10-20 12:17 GMT+02:00 Thierry Goubier <[hidden email]>:
Ok. The Pharo4 / Pharo5 versions have a better refactored interface for the external git commands, which may make it a bit easier to read. The Pharo3 version is functional, still. I will have a look to backport those changes to the Pharo3 branch. Thierry
|
|
|
In reply to this post by HilaireFernandes
Hilaire
what is the problem that you encounter to still be in Pharo3.0? Stef Le 20/10/15 12:13, Hilaire a écrit : > Le 20/10/2015 11:20, Thierry Goubier a écrit : >> So it looks very similar to a filetree + git workflow ? >> >> Any taker on adding a fossil interface to filetree with the same >> approach as GitFileTree ? >> >> Thierry > Which version of GitFileTree should I take for Pharo3? > > Hilaire > |
|
|
In reply to this post by Thierry Goubier
2015-10-20 12:21 GMT+02:00 Thierry Goubier <[hidden email]>:
Underway. It is integrated in the github filetree main repository in the pharo3.0 and pharo3.0_dev branches; I'll update the .mcz soon. Thierry
|
|
|
2015-10-20 16:07 GMT+02:00 Thierry Goubier <[hidden email]>:
Done. The configuration has been updated for Pharo3. Thierry |
|
|
In reply to this post by HilaireFernandes
6.0 Review Of Key Concepts
The fossil program is a self-contained stand-alone executable. Just put it somewhere on your PATH to install it. Use the clone or new commands to create a new repository. Use the open command to create a new source tree. Use the add and rm or delete commands to add and remove files from the local source tree. Use the commit command to create a new check-in. Use the update command to merge in changes from others. The push and pull commands can be used to share changes manually, but these things happen automatically in the default autosync mode. It looks like something that I can understand. I'm sure that other people will get bored by the complexity of git commands (because conceptually there not much in there). |
|
|
In reply to this post by HilaireFernandes
This is good to hear ....
I am pro-git, because well you have to pick an SCM to talk about and I do think that the collaboration tools for open source projects on github are superior to anything else... Git other than that I am glad that folks are finding that FileTree is working for other disk-based SCMs --- because that really is the point of FileTree:) It should also be possible to copy packages back and forth between a git-managed FileTree repository and a Fossil-managed Filetree repositor... Dale On 10/20/2015 02:09 AM, Hilaire wrote: > Hi, > > I have been trying Fossil with Filetree, and I was rather please by the > mutuals use of these tools. So I may share a few feedbacks. > Fossil[1] itself is a software to manage source code development. It is > very simple to install and data is saved in a single sqlite database. It > comes with source code management, bug tracker, web interface, wiki and > timeline tools. > > I was a bit afraid by the filetree atomic commit (one file per method) > to manage it without much headache with file based VCS. However fossil > comes with a nice command: 'fossil addremove' to add/remove the changed > files in the repo. So it went fine. > > So all in all, it is pretty nice if one want to move to a private souce > code management system with very little requirement. > > Hilaire > > [1] http://www.fossil-scm.org > |
|
|
In reply to this post by stepharo
Stef,
There is no problem. I just *lack time* to keep moving on DrGeo features and migrate to Pharo4.0 at the same time. I quickly try Dr. Geo code on Pharo4 and realize it will need some work and lot of user testing to get DrGeo as robust as it is now. We will conduct end user experiment in primary school, so I don't think migrating now will be a good idea. I will very likely skip directly to Pharo 5.0, as I did from 1.4 to Pharo 3.0 directly. Hilaire Le 20/10/2015 16:02, stepharo a écrit : > Hilaire > > what is the problem that you encounter to still be in Pharo3.0? > > Stef > > > Le 20/10/15 12:13, Hilaire a écrit : >> Le 20/10/2015 11:20, Thierry Goubier a écrit : >>> So it looks very similar to a filetree + git workflow ? >>> >>> Any taker on adding a fossil interface to filetree with the same >>> approach as GitFileTree ? >>> >>> Thierry >> Which version of GitFileTree should I take for Pharo3? >> >> Hilaire >> > > > -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
|
|
In reply to this post by Thierry Goubier
Le 20/10/2015 16:32, Thierry Goubier a écrit :
> Done. The configuration has been updated for Pharo3. > Où dois-je regarder ? -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
|
|
Le 21/10/2015 21:09, Hilaire a écrit :
> Le 20/10/2015 16:32, Thierry Goubier a écrit : >> Done. The configuration has been updated for Pharo3. >> > > Où dois-je regarder ? > Look the following methods in MCFileTreeGitRepository, protocole git querying: gitBranchs gitCloneRepositoryAndCheckoutIn: gitNeedPush gitPull gitPush gitVersions gitVersionsForPackage: and in i/o writeRepositoryProperties and in MCFileTreeGitStReader zip The two definition related methods (#zipForDefinition:, #gitVersionsForDefinition:in:) are optional: they allow you to query method versions in the git repository as if it was the change set, and they are only available from the AltBrowser IDE. For an adaptation to Fossil, I believe all the main code can be reused (same use of SHA-1 commit ids, branches, monticello metadata recreation) with very similar commands (fossil x instead of git x). The main difference being, as far as I know, the use of git archive to retrieve a zip containing a version of a package; I haven't seen the equivalent command in Fossil. The base OSProcess / ProcessWrapper code is a bit long, but I prefer to keep it that way for reliability reasons: it took me a long time (literaly years) to reach a stable solution on Unix. (MCFileTreeGitRepository>>#runOSProcessGitCommand:in:) Thierry |
|
|
Thanks for the details it will be helpful, but I wanted to know where is
the .mcz package? Hilaire Le 21/10/2015 21:29, Thierry Goubier a écrit : > Le 21/10/2015 21:09, Hilaire a écrit : >> Le 20/10/2015 16:32, Thierry Goubier a écrit : >>> Done. The configuration has been updated for Pharo3. >>> >> >> Où dois-je regarder ? >> > > Look the following methods in MCFileTreeGitRepository, > protocole git querying: > > gitBranchs > gitCloneRepositoryAndCheckoutIn: > gitNeedPush > gitPull > gitPush > gitVersions > gitVersionsForPackage: > > and in i/o > > writeRepositoryProperties > > and in MCFileTreeGitStReader > > zip > > The two definition related methods (#zipForDefinition:, > #gitVersionsForDefinition:in:) are optional: they allow you to query > method versions in the git repository as if it was the change set, and > they are only available from the AltBrowser IDE. > > For an adaptation to Fossil, I believe all the main code can be reused > (same use of SHA-1 commit ids, branches, monticello metadata > recreation) with very similar commands (fossil x instead of git x). > The main difference being, as far as I know, the use of git archive to > retrieve a zip containing a version of a package; I haven't seen the > equivalent command in Fossil. > > The base OSProcess / ProcessWrapper code is a bit long, but I prefer > to keep it that way for reliability reasons: it took me a long time > (literaly years) to reach a stable solution on Unix. > (MCFileTreeGitRepository>>#runOSProcessGitCommand:in:) > > Thierry > > -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
|
|
Le 21/10/2015 21:58, Hilaire a écrit :
> Thanks for the details it will be helpful, but I wanted to know where is > the .mcz package? Just use the ConfigurationOfGitFileTree available in your Configuration browser in the image ;) Or Metacello new configuration: 'GitFileTree'; repository: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main'; load Thierry > Hilaire > > > Le 21/10/2015 21:29, Thierry Goubier a écrit : >> Le 21/10/2015 21:09, Hilaire a écrit : >>> Le 20/10/2015 16:32, Thierry Goubier a écrit : >>>> Done. The configuration has been updated for Pharo3. >>>> >>> >>> Où dois-je regarder ? >>> >> >> Look the following methods in MCFileTreeGitRepository, >> protocole git querying: >> >> gitBranchs >> gitCloneRepositoryAndCheckoutIn: >> gitNeedPush >> gitPull >> gitPush >> gitVersions >> gitVersionsForPackage: >> >> and in i/o >> >> writeRepositoryProperties >> >> and in MCFileTreeGitStReader >> >> zip >> >> The two definition related methods (#zipForDefinition:, >> #gitVersionsForDefinition:in:) are optional: they allow you to query >> method versions in the git repository as if it was the change set, and >> they are only available from the AltBrowser IDE. >> >> For an adaptation to Fossil, I believe all the main code can be reused >> (same use of SHA-1 commit ids, branches, monticello metadata >> recreation) with very similar commands (fossil x instead of git x). >> The main difference being, as far as I know, the use of git archive to >> retrieve a zip containing a version of a package; I haven't seen the >> equivalent command in Fossil. >> >> The base OSProcess / ProcessWrapper code is a bit long, but I prefer >> to keep it that way for reliability reasons: it took me a long time >> (literaly years) to reach a stable solution on Unix. >> (MCFileTreeGitRepository>>#runOSProcessGitCommand:in:) >> >> Thierry >> >> > > |
|
|
In reply to this post by stepharo
Hi Stef,
Thanks for this review. Because of its portability and simplicity I use it for every project I have. Since 2011 I'm writing my thesis as a solo "open research" exercise (before it get fashioned ;-) time line at [1]). Now I used in conjunction with STON to write all the thesis inside pharo, nothing fancy, just put STON grafoscopio trees inside a fossil repo a run commit from shell. Still I need to make STON DVCS friendly (long strings made fossil to treat it as a binary, but I haven't had the time to explore Sven's advice on this. My proposal on "pocket infrastructures"[2] tries to put Pharo, Fossil and SQLite as a bootstrapable (install pharo and it installs the rest) self contained system for interactive writing. [1] http://mutabit.com/repos.fossil/doctorado-offray/timeline?n=500&y=all&v=0 [2] https://www.newschallenge.org/challenge/data/evaluation/data-kitchen-frictionless-data-moldable-tools-pocket-infrastructures-permanent-workshops-for-community-empowerment May Jimmie, Hilaire and you have more success into putting Fossil in the community radar :-). Cheers, Offray On 20/10/15 11:03, stepharo wrote: > 6.0 Review Of Key Concepts > > The fossil program is a self-contained stand-alone executable. Just > put it somewhere on your PATH to install it. > Use the clone or new commands to create a new repository. > Use the open command to create a new source tree. > Use the add and rm or delete commands to add and remove files from the > local source tree. > Use the commit command to create a new check-in. > Use the update command to merge in changes from others. > The push and pull commands can be used to share changes manually, but > these things happen automatically in the default autosync mode. > > > It looks like something that I can understand. > I'm sure that other people will get bored by the complexity of git > commands (because conceptually there not much in there). > > > |
|
|
In reply to this post by Dale Henrichs-3
Hi,
On 20/10/15 13:34, Dale Henrichs wrote: > This is good to hear .... > > I am pro-git, because well you have to pick an SCM to talk about and I > do think that the collaboration tools for open source projects on > github are superior to anything else... > My friends think the same, but usually they don't know "anything else", specially Fossil :-). They just picked what the majority did. > Git other than that I am glad that folks are finding that FileTree is > working for other disk-based SCMs --- because that really is the point > of FileTree:) > Yes, nice to know. > It should also be possible to copy packages back and forth between a > git-managed FileTree repository and a Fossil-managed Filetree > repositor... > It is. Fossil have an import command, somewhere. Cheers, Offray |
|
|
Hi Offray What fossil hosting service do you recommend ? Thanks On Wed, Oct 21, 2015 at 6:07 PM, Offray Vladimir Luna Cárdenas <[hidden email]> wrote: Hi, Bernardo E.C. Sent from a cheap desktop computer in South America. |
|
|
Bernardo,
I host my own repos. Is really easy[1]. In my case was just a matter of enabling cgi on lighttpd[2] and adding the lines at [3] to the lighttpd.conf file. There is a place that offers fossil hosting as a service[4] and at some time I tried to make my own in web2py (but code is not maintained anymore). [1] http://fossil-scm.org/index.html/doc/trunk/www/server.wiki [2] http://lighttpd.net/ ~[3]~~~ # Enabling fossil cgi.assign = ( ".fossil" => "/usr/bin/fossil" ) ~~~~~ [4] http://chiselapp.com/ Hope it helps, Offray Ps: About your signature, just curious to know where is that desktop computer in Latin America. On 21/10/15 18:24, Bernardo Ezequiel
Contreras wrote:
|
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |