Improve TLE data management

[csete]

Improve TLE data management

[cureton]

Hi Alex,
I have been thinking about a solution for this for the trsp files. Obviouly they are less dynamic that the TLE files however there may be a parallels. With the updates I have just submitted a pull-request for I realise that it will overwrite user developed trsp files with the distributed ones shoud a user upgrde the release of gpredict.

One solution is to distribute the trsp files in the distribution in the /usr/share/gpredit/trsp location, however upon loading the trsp files, first look in the user area first (~/.config/Gpredict/trsp), then failing that look in the /usr/share/gpredict/trsp location. That was the user can overwrite the system files as they wish.

This approach would also allow the distribution of the trsp and tle files as "volitile" packages in a lnux distribution at they contain only data and not code. Much the same was as the tzdata files are distributed. Therefore updates to "stable" distribution release can be release in a timely manner. (I'm looking at debian here)

This approach suits the trsp files better than the TLE file, but I think the approach has some merit.
What do you think?

[csete]

I think today it makes very little sense to distribute any satellite data files with gpredict. For most users it will be possible to download the current data when they first run the application.

[alexf91]

A seperate Github repository for the transponder files might be good.
This way, users of an official release could also update their transponder data and the files would still be under version control.

[csete]

Don't think I will ever have time to finish this, so I am working on a simplified version of this.