I am not sure it was in the same discussion. Anyway. The dependency on Renaissance is not a problem at all.

> I even made the case that libEOModeler could be
> shipped with DBModeler here

It is exactly what we are doing.

Perhaps we should use the opportunity of the soname bump (all GDL2 libraries need it AFAICT) to split the package in a better way. You are correct that the right split is into non-gui and gui stuff. Maybe we could lump the adaptors together (MySQL+Postgres in one package) at the expense of the gui<->non-gui split. That's what I did for SQLClient (all 4 bundles in the library package), as it doesn't make sense to have separate packages for a few KB.
The additional dependency on libmsysqlclient or libpq is negligible compared to the things GUI/Back pull in.

We can try to ship both apps with a bit of effort. EOModeler is distributed as a private library in Debian, because David Ayers once told us it was going to undergo major changes. Is the current split what he meant back then? What are the advantages of the new app over DBModeler? Not working with the palette is a big minus AFAICT.

On DBModeler, do as you see fit, AFAICT EOModelEditor isn't a complete replacement for DBModeler since when changing the libEOModeler framework it will no longer work with GDL2Palette,
and isn't compatible with the original EOModeler framework in EOF

If there is interest in DBModeler i'll set up a git repository for it somewhere and rename the libraries to avoid the clashes that EOModelEditor introduced, though I don't really plan on spending any further effort on it unless there is interest.

Hi, i'm a co-maintainer of the gnustep-dl2 debian package and was wondering if are there any plannings for a new release of the project. The package is now heavily patched to follow the latest trunk fixes and it is becoming a bit difficult to keep track of all the changes.

Moreover, i would like to ask your opinion about what should be the future steps to maintain the package on debian. I've seen that there is an incompatible fork of EOModel and a new app, EOModelEditor, that seems to have the same functionality of DBModeler. Should these replace the old ones in the package?