In the Gofer #push case, it's quite strange... some classes end up the wrong
package, and some don't get output at all.
It seems to work using Gofer #push when each is in its own repository
folder, and it also works with them all in the same folder when using
Monticello Browser's 'save' button.
P
I'm getting a DNU for UnixFileDirectory on #pathString.
Additionally, I tried the Gofer #push command with the basic filetree://
with multiple packages but it failed to save a few and didn't raise an
error. A bit unsettling... filetree is supposed to be 1.4 compatible, yes?
--
View this message
Oh, I'm having trouble adding a gitfiletree repository, do you support Pharo
1.4?
--
View this message in context:
http://forum.world.st/Git-filetree-workflow-tp4701465p4701541.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Thierry,
Many thanks for your prompt reply! I did find gitfiletree on smalltalk hub
while I was doing some research, but I thought that filetree was
specifically designed to be used with git, so I tried that first.
I'll see how it works in my case. Just one question- how do I import the mcz
histo
Furthermore, I just had a poke around the filetree of a package, and found
the `monticello.meta/version` file. This seems to contain information on the
monticello commits. Do I need this? I'd rather only have git commit
messages. Perhaps this file could be ignored by git?
--
View this message in
I work on a project that uses smalltalk as a part of a larger system. We
version control most of the code (Objective-C, mainly) using Git. Currently
the repo has a build script under version control which specifies the
monticello package versions to fetch for a given commit. This works okay,
and ke
