Esteban Lorenzano wrote:
the problem is that tonel relies in a .properties file to know a repository
format.
and for backward compatibility, if this .properties file is not present,
iceberg assumes the repository is a plain old “filetree” repository.
so, until we figure out how to provide both things (a nice tonel switch and
backwar compatibility), the workaround is to commit a .properties file into you
root repository, with this form:
{
#format : #tonel
}
and of course, that’s before doing anything image-side.
Yeah, that was maybe what I actually did, somehow. I faintly remember
only doing something with .properties first... maybe I achieved it by
getting to the newly created repo instance by some allInstances
filtering and setting it to tonel format by some message send then
committing it empty so .properties got there... anyway thanks for
clarifying it for the next time.
cheers,
Esteban
On 9 May 2018, at 12:21, he...@mailbox.sk wrote:
Yes, it is insanely hard to write project in tonel format. Needs lot of hacking
here and there, setting the setting itself is not helpful. I managed to,
somehow, but I forgot the algorithm already. I am dreadful as to when I will
need to do it again. Takes lots of time and nerves.
Herby
On May 9, 2018 11:54:56 AM GMT+02:00, Tim Mackinnon <tim@testit.works> wrote:
Hi guys - With all the talk about iceberg changes, I’ve stayed away
from it for a bit (6 months) - but downloaded a new 6.1 image a few
weeks ago and went to version some stuff yesterday into a new project.
Iceberg seems a bit more stable - but it still seems to write out
individual methods as files which I thought had been changed? Am I
doing something wrong - or do i need to set something?
Tim
Sent from my iPhone
