The following warnings occurred: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Warning [2] Undefined array key "lockoutexpiry" - Line: 94 - File: global.php PHP 8.1.27 (Linux)
|
Linux 64 and 32 bit packages for latest vdrift - Printable Version +- Forums (https://www.vdrift.net/Forum) +-- Forum: Community (https://www.vdrift.net/Forum/forumdisplay.php?fid=3) +--- Forum: Feature Requests (https://www.vdrift.net/Forum/forumdisplay.php?fid=6) +--- Thread: Linux 64 and 32 bit packages for latest vdrift (/showthread.php?tid=1027) Pages:
1
2
|
Linux 64 and 32 bit packages for latest vdrift - nzadlithium - 12-10-2008 Hey I've been trying to install vdrift for a while now (and failing miserably, but that can go into my post in the help section :p), I noticed that the packages you have for linux are out of date, and that they are done via autopackage. I would like to use the latest version and thus have to compile from source :S Autopackage does not currently support 64bit (they do say you can install 32bit packages on 64bit, but when i try to install from autopackage it just tells me that every thing is the wrong elf class even though i have the 32bit versions of the libs installed as well), so maybe you could either ditch autopackage, or provide your 32bit packages via autopackage, and 64bit via an already compiled tar.gz? (to keep it distro neutral). Or possibly you could just make an rpm/deb. And then if people want to install it on something that uses a dif package system they can use alien to convert it? So pretty much can we have working 32bit and 64bit installers for the latest version of vdrift on linux? - joevenzon - 12-10-2008 We haven't had any binary releases for linux in a while because no one has had the time and/or know-how to do them. If you're up to the challenge, we could use the help. - nzadlithium - 12-10-2008 ah ok. Well if I can get it to compile i'll have a go at making packages - joevenzon - 12-12-2008 Okay cool, if you need any help with the compilation stuff let me know. - Tom - 06-25-2009 You can get binary packages from here (as exemple): https://admin.fedoraproject.org/community/?package=vdrift#package_maintenance/details/downloads Maybe you could make a link on the website...? Tom - fudje - 06-26-2009 I could probably have a go at putting together the necessary tree to make .deb packages - these would normally apply to any debian-derived system. Should be fairly mundane due to using scons. Building Deb packages with scons - bogdanbiv - 06-26-2009 Here is a tutorial about making .deb packages with scons: http://www.qandr.org/quentin/writings/debscons It requires putting this lines at the end of the SConstruct script: Code: # package target build as a Debian package So far I have learned about DEBs, but I am having problems with Scons and Python, which are a little unfamiliar. I couldn't figure yet where should the DEBFILES point to... where to put vdrift documentation, where to put executable files (though I assume it'll be something around /usr/bin/vdrift) I'll try to put the script I've made so far in the discussion section on http://wiki.vdrift.net/Compiling The file deb/debConstruct.py should contain: Code: # -*- coding: utf-8 -*- Hopefully, if people improve this to really work it will be included in the SCons build. UPDATE: So far I have only have copied the vdrift data to a packaging folder. I have only thought about making a single DEB package for the whole work. But what if we would do two packages a vdrift and a vdrift-data (such as openarena and openarena-data)? What advantages would that offer? - fudje - 06-26-2009 Wow, and I was just going to use debhelper. Splitting it out into binary and data files would allow different levels of data package - you could have a 'full' package and a 'minimal' package but only have to packages the binaries once. It would also allow you to retain data and install new binaries for when they changed but data didn't (which is fairly normal). a few points - bogdanbiv - 06-27-2009 1) I have a small problem: the script that was given as an example for building DEBs from scons processes every single file, but I don't know how to cope with so many files under a deep tree: there are over 1000 files here and lumping them together in a single file just doesn't cut it for me. If I am to finish this I believe I should build a list of files in every single folder: just as SConscript main file calls data/SConscript which in turn calls data/carparts/SConscript, which in turn calls... ok I guess people can figure the rest I should call a subscript in every folder.... or maybe I can build the DEBFILES array in every single SConscript in every subfolder gather them arround and process them at in the end file. Don't rely too much on my work: I'm just learning Python, SCons and DEB packages as I go (ok I had build 2 example DEB packages but that's hardly a deep experience) 2) The debhelper option is good too, but I just didn't figure out how to do it, where to find files and stuff (the build folder only contains binary files, I didn't find the data/carparts folder at first). Maybe you will like to test the checkinstall utility for building DEB packages, as it's very wizzard-like. Maybe I could help building the debhelper version too if you could help finding where some files go when installing: where does the documentation files go? 3) Ok, I just found that the tools folder contains Deb packaging files from 2006. I'll try to see if I can figure something out of it (although old I hope most of the info is still valid). - bogdanbiv - 06-27-2009 UPDATE: DEBFILES, a gobal variable array which tracks where each file in the package should go, would be highly distribution dependant, meaning that the documentation would go into some folder for Debian distributions and in another folder for other distributions, so if Fedora people decide they want to build RPMs with SCons they would also need to make some kind of RPMFILES or FedoraFILES. Suddenly it doesn't sound like a good idea. What do you think? - fudje - 06-27-2009 You'd want to build your file list using globbing... - bogdanbiv - 06-27-2009 You mean global variables? Isn't it a better idea to add this list into the env global variable? Could this be another SCons target (more or less in the official scons build script)? - fudje - 06-27-2009 No, file globbing.... I'm sure python has utilities somewhere for building lists from glob patterns, I'm just not sure where (Perl junkie here :roll Actually now that I'm looking I can find anything for recursive matching which is why you'd want. But yeah, you've certainly put your thumb on why having one packaging script for all distributions rarely works properly (and why most projects are happy to let the distro vendor do the packaging). - bogdanbiv - 06-28-2009 I Found out about file globbing http://docs.python.org/library/glob.html - it seems to be somewhere in between RegExp ([a-z][0-9]+) and wildcard search (*, ?) I'm trying to become an Ubuntu maintainer btw, so you can still say the distro vendor does the packaging. - joevenzon - 06-28-2009 It would be nice to have a generic autopackage (or some other simple installer system) binary available from the VDrift site that would work with many different distributions (in addition to the packages that the distro maintainers make). I see a lot of forum posts from folks who have problems with their distribution's binary (or it's out of date) and would like to try the latest release without having to compile it themselves. |