> 1) Have you got the scripts? would look to see how its done. > Yes, you first have to use the: http://brisa.homelinux.net/fgfs/download_and_compile-2.0.0.sh (save it in an empty folder and run it) to have fgfs 2.0 up and runnning
then: http://brisa.homelinux.net/fgfs/debCreator-2.0.0.tar.gz unpackit and change the fift line ORI_PATH= to point to the folder you build FlightGear run it. it will recompile and build packages. > 2) As far as "where to put them", Launchpad PPA's would be an obvious > choice. > I would like to do it, but it seems to me you have to work with src debs, and you can't send them binary debs. And since these are not programs, bat data for FlightGear don't know what to do. > 3) Can the "deb's" be created via an automated process.. eg check is > changed in cvs, make package, upload. > There is an other script that creates packages for cvs version, the script compare the compilation folder with the local folder and if it finds files differences it will build a new package for aircraft with new version number. here: http://brisa.homelinux.net/fgfs/download_and_compile.sh and after: http://brisa.homelinux.net/fgfs/debCreator.tar.gz If any problem, let me know. > pete Cheers Francesco ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
