[pkg-fgfs-crew] Some ideas for the packaging of the next FlightGear release

[Ove Kåven]

Den 02. aug. 2011 14:13, skrev Christopher Baines:
> fgfs-base-aircraft       - containing the aircraft from the base release
>                           - provides fgfs-aircraft
> fgfs-base-scenery         - containing the scenery from the base release
>                           - provides fgfs-scenery
> fgfs-base-models          - containing the models from the base release
>                           - provides fgfs-models

The existing packages are named fgfs-aircraft-base and fgfs-models-base,
as I recall. This is for consistency with other fgfs-aircraft-* packages
and such, and I'd like to keep that.

> This dependency structure will resolve
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618890
> and better represents the true package relationships. What does everyone
> think?

The concept is probably OK, but the problem of implementing it remains...

> Ove, you have been brilliant fixing the transition issues with
> openscenegraph, do you intend to package version 2.4.0?

Sure. I'll look at it this weekend.

There's also a significant chance I'll do a little bit of other work on
FlightGear soon, due to a commitment I've recently made. Perhaps I'll
come up with a solution for TerraSync then.

By the way, I was a bit annoyed at noticing that discussion where you
stated that you were going to package the new release and start
packaging from scratch, without telling me about it. At present, the
packages are still my responsibility. I do appreciate getting help and
patches, and your skills do seem to have improved recently, but I
haven't given anyone else permission to mess with the FlightGear
packages yet. And certainly, in order to completely repackage it, then
you'd need that permission. For packages in Debian, that's the general
rule even if the current maintainer sucks (Developer's Reference,
section 5.9.5). So it was a bit disappointing to see...