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

[Christopher Baines]

According to the FlightGear development mailing list FlightGear 2.4.0
will be released in a bit more than two weeks [1]. I would really like
it if we could get some packages out for this release sometime close to
this. I have a full time job (working for Debian in the GSoC program)
but still have quite a bit of free time to spend on packaging FlightGear
and the other jobs mentioned below.

I have had a few ideas for the packaging for the next release. So in my
opinion it would be good to release the following packages:
flightgear            - containing everything as before except terrasync
              - depends fgfs-aircraft fgfs-scenery fgfs-models fgfs-base
fgfs-base                 - not containing scenery, models or aircraft
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
fgfs-terrasync            - from the flightgear source package
                          - provides fgfs-scenery fgfs-models
fgfs-aircraft-military    - good quality military aircraft
                          - provides fgfs-aircraft
fgfs-aircraft-historical  - good quality historical aircraft
                          - provides fgfs-aircraft
fgfs-aircraft-helicopters - good quality helicopters
                          - provides fgfs-aircraft
fgfs-aircraft-civilian    - good quality civilian aircraft
                          - provides fgfs-aircraft
fgfs-aircraft-airliners   - good quality airliners aircraft
                          - provides fgfs-aircraft

plus of cause simgear* fgrun and fgo. The fgfs-aircraft-* packages will
probably be from a single source package fgfs-aircraft-extra. 

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?

It would be brilliant (but not a necessity) if the fgfs-terrasync
package properly set up terrasync on the users system without and need
for user configuration? I, however probably do not know enough about the
security implications of implementing it as a kind of system service to
do this at the moment. 

I also would like to add some instructions to the Debian wiki on: 
- installing flightgear (how to best use the structure above)
- installing scenery blocks from tarballs 
- setting up terrasync 
- and installing aircraft that are not packaged 

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

Anyone have any comments, suggestions or offers of help?

Thanks,

Chris

[1]
http://sourceforge.net/mailarchive/forum.php?thread_name=CADt7PXPpY2M5eQHdDk0LDgHF8Zpc-rfvFY70-6RMXgxvBs1qfQ%40mail.gmail.com&forum_name=flightgear-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-fgfs-crew/attachments/20110802/c13dd176/attachment.pgp>