Hi! KFlog is a KDE Flight Logger, a program for (glider) pilots. For a good description and screenshots i suggest you take a look at http://www.kflog.org/ This tools is aimed at pilots, so i did put it in app-aviation first. But it might be a better idea to put it in app-misc, this would also be my suggestion. You can download KFlog directly from http://www.kflog.org/, it is totally free (GPL-2), nevertheless it has been mentioned in various aviation concerned magazines. Thanks!
Created attachment 29760 [details] kflog-2.1.1.ebuild
*** Bug 48577 has been marked as a duplicate of this bug. ***
sound like fun. let me do a few checks.
Can you give me a bit more info as to how the mapfiles, airspace and airfields are set up on your computer. I'm planning on including some files of these in the distro and providing a bit more info on how to set this program up. Also I'm planning on making /usr/share/apps/kflog/mapdata (and dirs below perms = root:users g+rw so everyone can share the same data. As for dependancies - look at what kind of things are mentioned in the ./configure part of the compulation - this will give you some DEPENDS. E.g. sys-apps/gawk sys-devel/gettext sys-apps/grep sys-devel/gcc virtual/glibc sys-libs/zlib seemed to be checked for during the installation. For runtime depends I use the commandline just to check: ldd /usr/bin/kflog | cut -f3 -d ' ' | xargs -n1 qpkg -f |sort | uniq Having said that I'm beginning to get a reputation as a dependancy freak. Doesn't hurt to be too cautious.
Hi! Regarding mapfiles etc. Aispace and Airfields can be found at http://maproom.kflog.org/index.php?lang=en&content=aero_map.php for the moment. Mapfiles: http://maproom.kflog.org/index.php?lang=en&content=select.php As you can see this lets you download the files that YOU need - someone living in Australia wouldn't download aispace/airfields and maps for India for example. If you want to include a map I suggest we make an additional ebuild, e.g. kflog-africa-20040512.ebuild and so on, that includes the specific data. NOTE: be aware that aispaces and airfield data changes. That's why it is importaint to include the valit-until-date in the ebuild (like kflog-africa-20040512.ebuild, meaning this data is valit until 2004-05-12). But I'm afraid that's a lot of ebuilds to create and check every 28 days... Another thing - I did download _all_ the mapfiles once - 1.8 GB on my disk wasted for the terrain data of Alaska and the rest of the world, where I'll never be flying... Permissions for /usr/share/apps/kflog/mapdata root:users g+rw is a good idea - I forgot about that... Where do I get "cut" from - no such command on my machine... Meanwhile thanks for you checking and for you effort. Andi.
I did some more research and I came to the conclusion that people should install the maps and airports and airspaces manually. Because: 1.) KFlog can download all required stuff when you need it (on the fly, so to say). 2.) No one needs all maps, you have to sit and study what you need anyway. 3.) The program is for glider pilots, this is a limited group of people. And even less of them use KDE (and Linux), it is okay to require a manual download. 4.) You have to update airspaces aprox. every 28 days, every pilot knows that's part of a flight preparation and so they do when they aim to make it good and safe. 5.) http://maproom.kflog.org/ is a good developed portal that makes it real easy to find the maps etc. that are required to work with KFlog in your area. It even tells you how to install the stuff... So i'd say the ebuild for kflog is enough. The permissions for the mapdata directory should be set correctly though. I had this wrong. Concerning the dependences-question: if KFlog sets up on KDE then it depends on KDE in the first place. I am pretty sure that KDE itself has a lot of dependencies (including zlib and libpng). Isn't it okay then to just make KFlog depend on KDE? Anyway, I think there's nothing more to it than this. Andi.
cut is in sys-apps/coreutils I'm definately not going to do a build per region for maps. I'm glad kflog downloads them - I didn't see the option though. I trust you it's there though. Thanks for your input. Any problems just tell me. As for dependancies - the acinclude.m4 in the kflog specifies a lot of libraries to directly include. If KDE changes in the future and nolonger needs one of these dependancies it could become unstuck.As mentioned in comment #4 - me = freak ;-) PS good use of pkg_postrm in your ebuild. commited to cvs in x11-misc. Thanks for a good ebuild and your help and advice.
