Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

migrate sources to metadataless format? #491

Open
estebanlm opened this issue Jun 12, 2018 · 5 comments
Open

migrate sources to metadataless format? #491

estebanlm opened this issue Jun 12, 2018 · 5 comments
Labels

Comments

@estebanlm
Copy link
Contributor

is not just that is impossible to work with iceberg, is also very annoying to work on branches :P
Can't we migrate to metadataless format?
I guess is available in all platforms now?

@jecisc
Copy link
Contributor

jecisc commented Jun 12, 2018

The problem is that currently, it's possible to update Metacello in very old Pharo because they can manage metadata full file tree.

If Metacello move to a Metadataless format we need to update the update scripts to maybe install the last metadatafull version of Metacello and only then the stable version of Metacello.

@estebanlm
Copy link
Contributor Author

in a point, we need to move forward.
how many versions we will support back?
I understand we need to keep support for a fair amount of them... but we cannot have eternal backward compatibility.

And the problem with the metadataful format is that, in practice, is a one man work (yes, there is the merge driver, and it helps a lot, but well... )

@krono
Copy link
Collaborator

krono commented Jun 12, 2018

Please note that Metacello is a project that lives beyond the recent Pharo versions. What I mean is that, not only older Pharo versions might have a problem with metadataless, but also maybe a GemStone or a Squeak that are not the most recent. Going forward is cool, but playing nice with all kids on the playground is also cool (from the Metacello implementations point of view).

Maybe we can find a way to have metadataless with all players.

That being said, it is probably hard to maintain proper history. and Just dropping the commit history seems a bit sad to me.

@estebanlm
Copy link
Contributor Author

estebanlm commented Jun 12, 2018

But this is a problem also for squeak and gemstone: you cannot properly work on branches with metadataful. And as far as I know metacello already can work with metadataless in most versions.

Now, the history problem: is not a problem, there are tools to migrate sources with history. But yes, history resides in other place than a text file committed with each version. And yes, you need tooling if you want to use it from your dialect (Pharo already has them, but that's because we decided to "take the bull by the horns" and develop them).

@jecisc
Copy link
Contributor

jecisc commented Jun 12, 2018

Hi @krono

I think it's one of the reasons why it's with the "question" tag.

Can you explain the current situation of Metacello for squeak please?

Personally, I don't know much about Squeak so what is the current stable version? Would it be able to update Metacello if it was metadataless? If yes, for how many past versions of Squeak is it possible?

If the last versions are able to update Metacello if it was metadataless and if we are able to produce a script to first update to the latest metadatafull version then to the current metadataless version it could work no?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants