Follow-up Comment #3, bug #42698 (project gnustep):
I recall that being more about limiting the number of debian packages, and
trying to find a good split of gui/non-gui,
I even made the case that libEOModeler could be shipped with DBModeler here
Follow-up Comment #4, bug #42698 (project gnustep):
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
Follow-up Comment #2, bug #42698 (project gnustep):
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
Follow-up Comment #5, bug #42698 (project gnustep):
(MySQL+Postgres in one package)
Of course I meant SQLite, not MySQL.
___
Reply to this item at:
http://savannah.gnu.org/bugs/?42698
___
URL:
http://savannah.gnu.org/bugs/?42698
Summary: Recommended future steps for gnustep-dl2 debian
package maintenance
Project: GNUstep
Submitted by: fgimenez
Submitted on: Mon 07 Jul 2014 07:11:31 PM CEST
Category: gdl2
Follow-up Comment #1, bug #42698 (project gnustep):
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
