While, I’m still interested in how share repositories works (and debunk some of
my myths about it ) - digging into this users issue (isn’t Fuel wonderful) - it
would seem that this image wasn’t created with share repositories on.
It looking down a very complicated stack (Metacello is very compli
Tim Mackinnon wrote
> how is this shared repository supposed to work?
While I initially liked the space efficiency of the shared approach, I
eventually gave up because it created too many (often obscure) problems. It
just doesn't seem to be a good match for git, although you can get away with
it i
And then the Pharo launcher folder suddenly appears as a 20GB folder...
Same league as a Maven .m2, albeit with a messier structure, full of copies
all over the place.
Is Cargo going to help us there?
Phil
On Wed, Mar 6, 2019 at 5:18 PM Sean P. DeNigris
wrote:
> Tim Mackinnon wrote
> > how
I couldn't find a "simple enough" solution to deal with that, so I
moved to emulated Linux [1].
I don't know if the long file path is a limitation of Windows itself or libgit2.
Because if it's the former, then I'll try this setting in Windows 10
and let you know if it works:
https://www.howtogeek
On 3/6/19 8:18 AM, Sean P. DeNigris wrote:
Tim Mackinnon wrote
how is this shared repository supposed to work?
While I initially liked the space efficiency of the shared approach, I
eventually gave up because it created too many (often obscure) problems. It
just doesn't seem to be a good matc
On Thu, 7 Mar 2019 at 02:16, Esteban Maringolo wrote:
> I couldn't find a "simple enough" solution to deal with that, so I
> moved to emulated Linux [1].
>
> I don't know if the long file path is a limitation of Windows itself or
> libgit2.
>
Its a combination, but for our purposes the limitatio
