On Mon, 11 Apr 2005 14:47:30 +0200, Jimmy wrote in message <[EMAIL PROTECTED]>:
> Nick Coleman wrote: > > Hi All, > > > > I've just changed from many years of Mandrake to Debian Sarge. One > > thing I noticed when researching the move is lots of dire warnings > > about not polluting the filetree with non-Deb apps. > > > > I'm pretty familiar with compiling FG from source and CVS. Are > > there any special considerations I need to look out for when > > compiling FG for my Debian system? Things like PREFIX flags etc so > > that the binaries end up in the 'correct' place? (/usr/local is ok > > for anything non-Deb, yes?) > > > > Also, the current version of FG needs a newer version of plib than > > Sarge provides. What are the ramifications of installing both Deb > > plib and CVS plib at the same time? > > > > [just had a thought] Is there a way to build a deb package from a > > CVS source and install it using apt? That would get around the > > plib problem above. > > > > Sorry about the number of questions; this is my first install of a > > major non-Deb piece of software and I don't want to screw up the > > packaging system just yet. ;) > > Why don't you use > > apt-get install -t unstable fgfs-base ..that's not cvs, but do it anyway, and borrow the ideas from that set of packages to do your own package scripts. Also chk out the Debian Policy and developer resources, as those answers a lot of questions. Once you're done, you should be able to set up a _fully_ automatic FlightGear updater off cvs. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
