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 <hilaire@drgeo.eu>:
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.
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
Hilaire
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
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
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 <hilaire@drgeo.eu>:
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?
Hum, let me check what is the condition of this one. Thierry
Hilaire
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
2015-10-20 12:17 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:
2015-10-20 12:13 GMT+02:00 Hilaire <hilaire@drgeo.eu>:
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?
Hum, let me check what is the condition of this one.
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
Thierry
Hilaire
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
2015-10-20 12:21 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:
2015-10-20 12:17 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:
2015-10-20 12:13 GMT+02:00 Hilaire <hilaire@drgeo.eu>:
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?
Hum, let me check what is the condition of this one.
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.
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
Thierry
Thierry
Hilaire
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
2015-10-20 16:07 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:
2015-10-20 12:21 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:
2015-10-20 12:17 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:
2015-10-20 12:13 GMT+02:00 Hilaire <hilaire@drgeo.eu>:
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?
Hum, let me check what is the condition of this one.
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.
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.
Done. The configuration has been updated for Pharo3. Thierry
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
Le 21/10/2015 22:03, Thierry Goubier a écrit :
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
Okay, thanks. Not sure I can handle it right now, there are a lot of know-how about git and fossil implicated. Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
2015-10-22 10:40 GMT+02:00 Hilaire <hilaire@drgeo.eu>:
Le 21/10/2015 22:03, Thierry Goubier a écrit :
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
Okay, thanks. Not sure I can handle it right now, there are a lot of know-how about git and fossil implicated.
Yes, I guess so. Still, with all the people interested by Fossil, I think the motivation is there. And it would be nice to see a bit of refactoring to decouple the format from the specific commands used for the specific VCS. Thierry
Hilaire
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
Le 22/10/2015 10:47, Thierry Goubier a écrit :
Still, with all the people interested by Fossil, I think the motivation is there. And it would be nice to see a bit of refactoring to decouple the format from the specific commands used for the specific VCS.
Decoupling was my first though looking at the code. So it makes it bigger than a small hack as initially though ;) Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
2015-10-22 11:16 GMT+02:00 Hilaire <hilaire@drgeo.eu>:
Le 22/10/2015 10:47, Thierry Goubier a écrit :
Still, with all the people interested by Fossil, I think the motivation is there. And it would be nice to see a bit of refactoring to decouple the format from the specific commands used for the specific VCS.
Decoupling was my first though looking at the code. So it makes it bigger than a small hack as initially though ;)
Of course ;) It started as a small hack and has grown a bit since... Thierry
Hilaire
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
Le 22/10/2015 10:47, Thierry Goubier a écrit :
Yes, I guess so.
Still, with all the people interested by Fossil, I think the motivation is there. And it would be nice to see a bit of refactoring to decouple the format from the specific commands used for the specific VCS.
Thierry
I started to look at it creating abstracted super classes. But RB (refactoring tool I guess) bumped on the middle, try again, then went fine, ouf! Any sandbox where to commit? Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
Thierry and Hilaire, If you want to work together up on the github repo, that's up to you and Hilaire, if you have a github id, let me know and I will add you as a contributor on the project so that you two can work together ... Dale On 10/24/15 6:55 AM, Hilaire wrote:
Le 22/10/2015 10:47, Thierry Goubier a écrit :
Yes, I guess so.
Still, with all the people interested by Fossil, I think the motivation is there. And it would be nice to see a bit of refactoring to decouple the format from the specific commands used for the specific VCS.
Thierry I started to look at it creating abstracted super classes. But RB (refactoring tool I guess) bumped on the middle, try again, then went fine, ouf! Any sandbox where to commit?
Hilaire
Hilaire, Dale, the easiest would be to make a fork of filetree on github, and try from there. But a branch in the main filetree would work just as well, with the added benefit of the travis CI integration (and gitfiletree has tests in there). Running tests locally is often necessary, but setting it up is a bit more involved (but I should have that in a Makefile somewhere). Hilaire, if you prefer a Smalltalkhub project, just do so and I'll make regular merges back into filetree. Thierry Le 24/10/2015 18:04, Dale Henrichs a écrit :
Thierry and Hilaire,
If you want to work together up on the github repo, that's up to you and Hilaire, if you have a github id, let me know and I will add you as a contributor on the project so that you two can work together ...
Dale
On 10/24/15 6:55 AM, Hilaire wrote:
Le 22/10/2015 10:47, Thierry Goubier a écrit :
Yes, I guess so.
Still, with all the people interested by Fossil, I think the motivation is there. And it would be nice to see a bit of refactoring to decouple the format from the specific commands used for the specific VCS.
Thierry I started to look at it creating abstracted super classes. But RB (refactoring tool I guess) bumped on the middle, try again, then went fine, ouf! Any sandbox where to commit?
Hilaire
I was not aware filetree need to be modified as well? But wait, I can use it right now with Fossil, so I am bit lost. Hilaire Le 24/10/2015 18:44, Thierry Goubier a écrit :
Hilaire, Dale,
the easiest would be to make a fork of filetree on github, and try from there. But a branch in the main filetree would work just as well, with the added benefit of the travis CI integration (and gitfiletree has tests in there). Running tests locally is often necessary, but setting it up is a bit more involved (but I should have that in a Makefile somewhere).
Hilaire, if you prefer a Smalltalkhub project, just do so and I'll make regular merges back into filetree.
Thierry
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
Le 24/10/2015 18:56, Hilaire a écrit :
I was not aware filetree need to be modified as well? But wait, I can use it right now with Fossil, so I am bit lost.
No, no. This is just the development of GitFileTree is integrated inside the main FileTree repository. If you look at https://github.com/dalehenrich/filetree/tree/pharo4.0/repository, you'll find both MonticelloFileTree-Core and MonticelloFileTree-Git (as well as the Tests and the GitTests). Thierry
Hilaire
Le 24/10/2015 18:44, Thierry Goubier a écrit :
Hilaire, Dale,
the easiest would be to make a fork of filetree on github, and try from there. But a branch in the main filetree would work just as well, with the added benefit of the travis CI integration (and gitfiletree has tests in there). Running tests locally is often necessary, but setting it up is a bit more involved (but I should have that in a Makefile somewhere).
Hilaire, if you prefer a Smalltalkhub project, just do so and I'll make regular merges back into filetree.
Thierry
At the end of the day, I would assume that it would be possible to run travis-ci tests against a fossil repository which would be very useful to have ... but like I said, I'm fine with whatever you guys decide... Dale On 10/24/15 10:12 AM, Thierry Goubier wrote:
Le 24/10/2015 18:56, Hilaire a écrit :
I was not aware filetree need to be modified as well? But wait, I can use it right now with Fossil, so I am bit lost.
No, no. This is just the development of GitFileTree is integrated inside the main FileTree repository.
If you look at https://github.com/dalehenrich/filetree/tree/pharo4.0/repository, you'll find both MonticelloFileTree-Core and MonticelloFileTree-Git (as well as the Tests and the GitTests).
Thierry
Hilaire
Le 24/10/2015 18:44, Thierry Goubier a écrit :
Hilaire, Dale,
the easiest would be to make a fork of filetree on github, and try from there. But a branch in the main filetree would work just as well, with the added benefit of the travis CI integration (and gitfiletree has tests in there). Running tests locally is often necessary, but setting it up is a bit more involved (but I should have that in a Makefile somewhere).
Hilaire, if you prefer a Smalltalkhub project, just do so and I'll make regular merges back into filetree.
Thierry
Le 24/10/2015 18:44, Thierry Goubier a écrit :
Hilaire, if you prefer a Smalltalkhub project, just do so and I'll make regular merges back into filetree.
I commited to SqueakSource a few abstractions WIP http://ss3.gemstone.com/ss/istoa/ I more or less randomly abstracted the classes but can't test, I don't know much GIT. Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
2015-10-29 10:26 GMT+01:00 Hilaire <hilaire@drgeo.eu>:
Le 24/10/2015 18:44, Thierry Goubier a écrit :
Hilaire, if you prefer a Smalltalkhub project, just do so and I'll make regular merges back into filetree.
I commited to SqueakSource a few abstractions WIP http://ss3.gemstone.com/ss/istoa/ I more or less randomly abstracted the classes but can't test, I don't know much GIT.
Thanks. I'll have a look, make an issue on github, a branch, merge your changes and travis will test for us ;) Thierry
Hilaire
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
Hilaire, if you are interested in contributing, I would be willing to add you to the FileTree project up on GitHub ... Oops, unless you don't want to be:) Dale On 10/22/2015 01:40 AM, Hilaire wrote:
Le 21/10/2015 22:03, Thierry Goubier a écrit :
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 Okay, thanks. Not sure I can handle it right now, there are a lot of know-how about git and fossil implicated.
Hilaire
I will write you if needed, I am not there yet. Hilaire Le 22/10/2015 22:51, Dale Henrichs a écrit :
Hilaire, if you are interested in contributing, I would be willing to add you to the FileTree project up on GitHub ... Oops, unless you don't want to be:)
Dale
On 10/22/2015 01:40 AM, Hilaire wrote:
Le 21/10/2015 22:03, Thierry Goubier a écrit :
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 Okay, thanks. Not sure I can handle it right now, there are a lot of know-how about git and fossil implicated.
Hilaire
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
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
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
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.
I understand :)
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
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).
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-frictio... 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).
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
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 < offray@riseup.net> wrote:
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
-- 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:
Hi Offray What fossil hosting service do you recommend ?
Thanks
On Wed, Oct 21, 2015 at 6:07 PM, Offray Vladimir Luna Cárdenas <offray@riseup.net <mailto:offray@riseup.net>> wrote:
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
-- Bernardo E.C.
Sent from a cheap desktop computer in South America.
On Uto, 2015-10-20 at 11:09 +0200, Hilaire wrote: Hello, potential Pharo user here who just installed 5.0 image on his Debian Sid and researching whether Smalltalk (Pharo) can be used as language for writing some multi-platform opens-source apps...tried/evaluated several languages, but, considering I abandon idea to use {C(++), Java}, the the most pragmatical option so far is to use Object Pascal  and FPC/Lazarus(fpGUI), but someone recommended to inspect Smalltalk (I was tinkering with Digitalk looooooong ago while using OS2)...
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.
so I'm delighted to see the talk about using Fossil for VCS tool with Pharo.
So all in all, it is pretty nice if one want to move to a private souce code management system with very little requirement.
For those Git-lovers, there is plan by Dr Richard Hipp (author of Fossil) to provide support which "would allow you to "clone" repos off of GitHub.  Or to automatically sync your Fossil repositories on GitHub." (http://article.gmane.org/gmane.comp.version-control.fossil-scm .devel/580) Where can I find more about using Fossil with Pharo? Sincerely, Gour -- He who is regulated in his habits of eating, sleeping, recreation and work can mitigate all material pains by practicing the yoga system.
Hello, As for now, you have to use filetree, over fossil repo, but from Pharo you can only save to the repo, no way to fetch back I think. The GIT integration is more advanced with dedicated GIT package for Pharo. As a first iteration, I did some code modifications -- blindly I have to admit -- of the GIT package to decouple it from GIT, to later add fossil capability. Thierry was looking at integrating it in Jenkins job, to see if it is working or not. But if you are potential Pharo users, you should not waste your time on the CVS question but discover first the Pharo language and environment. There are other CVS options for Pharo you can use out of the box. Hilaire
So all in all, it is pretty nice if one want to move to a private souce code management system with very little requirement.
Where can I find more about using Fossil with Pharo?
Sincerely, Gour
-- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu
On Uto, 2015-12-22 at 15:23 +0100, Hilaire wrote:
As for now, you have to use filetree, over fossil repo, but from Pharo you can only save to the repo, no way to fetch back I think.
OK.
But if you are potential Pharo users, you should not waste your time on the CVS question but discover first the Pharo language and environment.
Sure, I'm really excited about it and exploring further. However, it's nice to find users within Pharo community who can see the merits of Fossil DVCS. Sincerely, Gour -- He is a perfect yogī who, by comparison to his own self, sees the true equality of all beings, in both their happiness and their distress, O Arjuna!
On Wed, Dec 23, 2015 at 09:38:20AM +0100, Saša Janiška wrote:
Sure, I'm really excited about it and exploring further. However, it's nice to find users within Pharo community who can see the merits of Fossil DVCS.
I use Fossil as personal wiki, VCS for config files, and ticketing system. I like it very much. For now I'm not bothered about integrating Fossil as a Pharo VCS though. I just use Monticello. Pierce
On Sri, 2015-12-23 at 20:01 +0800, Pierce Ng wrote:
For now I'm not bothered about integrating Fossil as a Pharo VCS though. I just use Monticello.
Is Monticello good-enough for collaboration with smaller team of devs? Sincerely, Gour --Â As a blazing fire turns firewood to ashes, O Arjuna, so does the fire of knowledge burn to ashes all reactions to material activities.
Hi, On 23/12/15 08:23, Saša Janiška wrote:
On Sri, 2015-12-23 at 20:01 +0800, Pierce Ng wrote:
For now I'm not bothered about integrating Fossil as a Pharo VCS though. I just use Monticello. Is Monticello good-enough for collaboration with smaller team of devs?
Yes, if you work only with Smalltalk code. About my uses of fossil and Pharo, my project, grafoscopio[1], uses Pharo for building a interactive documentation and data visualization environment with a tree like metaphor, and fossil as the DVCS for controlling all external artifacts to the image, including persistent document objects in STON[2], pandoc's markdown[3], latex and pdf and also graphics, figures. There is no explicit bridge between them right now in my project (which is pretty alpha), I just export from the image and keep my repos in sync from the command shell, but works fine for now. In a computing monoculture of overcomplex ways of doing programming and DVCS is refreshing to find a community where alternative ideas like Pharo and fossil and listened and used. [1] http://mutabit.com/grafoscopio/index.en.html [2] https://github.com/svenvc/ston/blob/master/ston-paper.md [3] http://pandoc.org/README.html#pandocs-markdown Cheers, Offray
On Sri, 2015-12-23 at 09:20 -0500, Offray Vladimir Luna Cárdenas wrote:
In a computing monoculture of overcomplex ways of doing programming and DVCS is refreshing to find a community where alternative ideas like Pharo and fossil and listened and used.
Indeed...now I'm into learning Pharo trying to adjust to some alternatives, but those will require to ask some additional questions. Sincerely, Gour --Â Even if you are considered to be the most sinful of all sinners, when you are situated in the boat of transcendental knowledge you will be able to cross over the ocean of miseries.
In a computing monoculture of overcomplex ways of doing programming and DVCS is refreshing to find a community where alternative ideas like Pharo and fossil and listened and used. Indeed...now I'm into learning Pharo trying to adjust to some alternatives, but those will require to ask some additional questions.
just ask do not hesitate.
Le 23/12/15 14:23, Saša Janiška a écrit :
On Sri, 2015-12-23 at 20:01 +0800, Pierce Ng wrote:
For now I'm not bothered about integrating Fossil as a Pharo VCS though. I just use Monticello. Is Monticello good-enough for collaboration with smaller team of devs?
of course. Pharo itself is developed like that. Moose too (check their number of packages). Stef
Sincerely, Gour
-- As a blazing fire turns firewood to ashes, O Arjuna, so does the fire of knowledge burn to ashes all reactions to material activities.
Le 22/12/15 11:39, Saša Janiška a écrit :
On Uto, 2015-10-20 at 11:09 +0200, Hilaire wrote:
Hello,
potential Pharo user here who just installed 5.0 image on his Debian Sid and researching whether Smalltalk (Pharo) can be used as language for writing some multi-platform opens-source apps...
Yes it does
tried/evaluated several languages, but, considering I abandon idea to use {C(++), Java}, the the most pragmatical option so far is to use Object Pascal and FPC/Lazarus(fpGUI), Pharo is really working on multi-platforms for real.
but someone recommended to inspect Smalltalk (I was tinkering with Digitalk looooooong ago while using OS2)...
Pay attention Pharo 50 is alpha.
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. so I'm delighted to see the talk about using Fossil for VCS tool with Pharo.
So all in all, it is pretty nice if one want to move to a private souce code management system with very little requirement. For those Git-lovers, there is plan by Dr Richard Hipp (author of Fossil) to provide support which "would allow you to "clone" repos off of GitHub. Or to automatically sync your Fossil repositories on GitHub." (http://article.gmane.org/gmane.comp.version-control.fossil-scm .devel/580)
Yes this is a smart move
Where can I find more about using Fossil with Pharo?
Sincerely, Gour
participants (8)
-
Bernardo Ezequiel Contreras -
Dale Henrichs -
Hilaire -
Offray Vladimir Luna Cárdenas -
Pierce Ng -
Saša Janiška -
stepharo -
Thierry Goubier