Re: How Debian Deals with Data
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Christopher,
On 16.07.2011 00:20, Christopher Baines wrote:
> The actual package would just contain the rules and checksums for the
> files it tries to fetch, but not the data itself, I think of this as a
> symbolic package. This approach in my opinion, would make packaging
> applications like FlightGear much easier, and improve the user
> experience.
just as a random alternative idea (where other people may judge whether
it is a good idea or not): There might still be benefits of letting dpkg
handle the installation stuff, even if you don't want to have such a
large amount of data in the archives.
This eases maintenance, updates and clean removal of packages. For your
purpose it might be worth to consider a half baked solution. For example
you could provide a meta package [*] which builds a new binary package
on the installation site. Without knowing anything about FlightGear this
potentially seems a good solution to me. Your meta package could
download your stuff, apply some checksumming and then produce a new
binary package with the actual game data.
Take a look into the google-earth package for an example what I'm
thinking about. Their use case is of course different than yours, but
the idea is the same.
This binary package may ease installation, transportation and copying of
your game's data. By using some nifty dependencies along with
"Provides"/"Replaces" relationships you could even do some interesting
dependency magic there, although the direct usage of "dpkg" makes it a
bit tricky to benefit from it.
[*] please don't confuse my usage of "meta package" with its
archive-wide meaning for Debian here.
- --
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJOIM3IAAoJEMcrUe6dgPNtdyEQAK3VVNWiguTMvlFl9JW6Mnua
CBTFSDiBAw6Fbhtd4HKqGAe1nRrEkiMtczHnDjOUIKGI7+S9Z+M7nFAkRayz/KLr
FMCKxAFuvshxAbNQTUHob6IXk9R/9ZRzRpbMVDiGpkWHSM+I7Mq3PAU2Ix4F+1+j
D2JuCUSne9bpuxlFnf/xXZyMkBrHC99EWfoSg+okRI9V9lhVUurf1+bVosMDmium
R5v8KktpmFyYSQ9Ik00QAItUxJOkExNAvfdZ+l9bTU5KIGI/lfjOXAbbfASYJ7cL
TazM8TNeRadTqtWTC9KkhmplGLYBinNAZzcEPy0fSfGQdOd0u12dMwg1+Pqtmbfa
/ivqfRxxlP7mCTXBcq+97Kadh/44Ei3uzxdQ9BQ/ZNj5Po0mCvx6PValrRzRHmaf
+DVJhQdBec1ij+H0ouUdw+wzVRgUkL6RWz790jQ1xVB1wrKtwNnSaUiWGM3bQY/L
8eT/JiphCQvVx1ewaefA0q7pzYGT/ZlZ39TEMxtvfiHU+HPpLCPFUlmP8snp1/i+
lNOUwh+jdCQ2OOPt++LERq3a6ubuPtJWlYxEXOL2DZsNsiGRx12mG9hi2eZlGiAJ
emOp4PtuF1KNdSg/0Fl5sM1MeJk5FC1BKMf5+LgM27G2mrSKBcwWvqCvFXXofSBj
WB4Gbvo5RiH/EFIK6mve
=Q03t
-----END PGP SIGNATURE-----
Reply to: