On Jun 19, 2013, at 3:02 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote:
Hi Stephane,
but, if you have to introduce Pharo as a business-ready tool in a git workflow (or any other vcs for that matter), it's better to say that you can do it, no?
sure I was just trying to help to avoid to get exposed to too many difficulities at once.
Thierry
Le 19/06/2013 11:13, Stéphane Ducasse a écrit :
Hi I do not know your experience with smalltalk and pharo but pay attention because there are really few people working using git and pharo. I would be you I would concnetrate on the smalltalk part first,
Stef
On Jun 18, 2013, at 11:37 PM, Bahman Movaqar <Bahman@BahmanM.com> wrote:
Hmm...let's say I have the project initiated on git. How can I do the initial commit? Does it handle package dependencies?
Thanks, -- Bahman Movaqar (http://BahmanM.com)
ERP Evaluation, Implementation & Deployment Consultant PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) On Tuesday 18 June 2013 20:42:10 GOUBIER Thierry wrote:
They will have to clone your git repository, create the image with the gifiletree:// support (I think there is a mistake in the script), and add the repository as a gitfiletree:// repository to see all your packages.
You can also use Gofer in the image:
Gofer it url: 'gitfiletree://<path to git clone repo>/<subdirectory used for Pharo packages>/'; package: '<name of package>'; load
Or on the command line.
Thierry ________________________________________ De : Pharo-users [pharo-users-bounces@lists.pharo.org] de la part de Bahman Movaqar [Bahman@bahmanm.com] Date d'envoi : mardi 18 juin 2013 22:22 Ã : Any question about pharo is welcome Objet : Re: [Pharo-users] Pharo + git
Thanks for the info.
Now suppose I shared my code on git. How can others use it on their own image?
On Tuesday 18 June 2013 20:14:21 GOUBIER Thierry wrote:
Yes, you can use git with Pharo.
You need to get an extension called MonticelloFileTree, and you can add on top of it a MonticelloFileTree-Git which really integrates into git.
Main repository is there:
https://github.com/dalehenrich/filetree
And temporary instruction to try the latest gitfiletree:// stuff is (under Linux) :
git clone git://github.com/ThierryGoubier/filetree.git mkdir pharo cd pharo wget -O- get.pharo.org/20+vm | bash ./pharo Pharo.image config http://ss3.gemstone.com/ss/FileTree ConfigurationOfFileTree --install=1.0.2 ./pharo Pharo.image eval --save "Gofer new url: 'http://ss3.gemstone.com/ss/FileTree'; package: 'MonticelloFileTree-Core' constraint: [ :version | version author = 'ThierryGoubier' ]; load" ./pharo Pharo.image config http://ss3.gemstone.com/ss/MetaRepoForPharo20 ConfigurationOfOSProcess --install=stable ./pharo Pharo.image eval --save Gofer new url: \'filetree://`pwd`/../filetree/repository/\'\; package: \'MonticelloFileTree-Git\'\; load ./pharo Pharo.image eval --save \(MCWorkingCopy hasPackageNamed: \'MonticelloFileTree-Git\'\) repositoryGroup\ removeRepository: \( \'filetree://`pwd`/filetree/repository/\' asUrl mcRepositoryAsUser: nil withPassword: nil\)\;\ addRepository: \( \'gitfiletree://`pwd`/filetree/repository/\' asUrl mcRepositoryAsUser: nil withPassword: nil\)
It's really to get the latest :) It will be simpler in the future.
My workflow, for a git repo and pharo, is to have a Makefile with those commands, a gitignore for the pharo subdirectory, and a make clean to remove the pharo directory and download a fresh vm and image. It avoids storing the pharo image and package cache inside the git repository, as I used to do before ;)
Thierry
________________________________________ De : Pharo-users [pharo-users-bounces@lists.pharo.org] de la part de Bahman Movaqar [Bahman@bahmanm.com] Date d'envoi : mardi 18 juin 2013 21:38 Ã : pharo-users@lists.pharo.org Objet : [Pharo-users] Pharo + git
Hi all,
I've searched the net and found out the answer is most probably "no"; but it doesn't hurt to ask here:
Is it posssible to use `git' as the VCS backend for Pharo?
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95