Bug#499635: FreeOrion
Hi Markus,
On Mon, 22 Apr 2013 08:56:41 Markus Koschany wrote:
> finally Bullet has arrived and i have started to work on FreeOrion.
> Recently i figured out how to build FreeOrion with Debian's Multiarch
> version. The game works now and it is playable.
Fantastic, I'm looking forward to try it as soon as can.
> I intend to update the git repository with my changes during the next
> couple of days and i really would like to see you as co-maintainer given
> all the work you have already commited to FreeOrion.
Please commit whatever you have even if it's not perfect. :)
If you made the game playable it is already in better shape that it was when I
left it.
Unfortunately these days I can't dedicate much time to freeorion
co-maintenance so you pretty much on your own at least for some time. Sorry.
Eventually I might be back if time allows...
> * I think FreeOrion should be splitted in two source packages freeorion
> and freeorion-data. That would save us some bandwith.
As far as I understand the issue by splitting we can save some resources on
buildd servers. Is there are any other benefits given that we generate
orig.tar from single repository checkout?
In any case I trust you with this decision.
> * Copyright looks good so far, no show-stoppers.
I think I didn't finish copyright review so perhaps you're talking about
copyright that you didn't commit yet?
> * I intend to target the game for Main.
Great. :)
> * I agree with you that we should stick with FreeOrions's gigi fork. It
> is better maintained and we only need the library for the game. I
> have tested gigi as a standalone package and as part of FreeOrion's
> build process. I'm willing to create a separate package because i
> think it is easier to maintain in the long-run. At first it looks
> like more work but it is easier to spot errors and to fix bugs
> related to gigi. The rules file of FreeOrion also looks tidier. :)
> So i'm not afraid to package the library as libgigi-freeorion to make
> it clear that it is a FreeOrion fork of gigi in case someone intends
> to package the original library.
>
I trust you with this decision but I don't see any value in splitting
freorion's gigi to its own package whatever its name would be. Why don't we
just leave gigi's RFP open with comment that there is an embedded copy in
freeorion?
It's remain to be seen whenever gigi will be valuable for anything but
freeorion. In case if gigi ever mature into proper library it can be easily
splitted to its own package then.
I'm concerned about maintenance effort. It appears to me that even if
freeorion's "rules" may look tidier the overall maintenance effort for two
packages built from same source tree might be greater comparing to bundled
libgigi. Ultimately if separating gigi to its own package is convenient to you
it is enough for me to justify the effort (i.e. I'm not against it I just
don't see the value of standalone gigi package).
Best wishes,
Dmitry Smirnov
GPG key : 4096R/53968D1B
Reply to: