Linux packager needed ? - how can I help ? /where's the source?
#1
Posted 28 September 2011 - 07:49 PM
I can do that, but where do I find the software/source, and maybe somebody even have some basic instructions on how-to ?
Then I should be able to make .deb packages.
#2
Posted 28 September 2011 - 08:26 PM
#3
Posted 28 September 2011 - 10:25 PM
#4
Posted 12 November 2011 - 02:39 PM
K Wells, on 12 November 2011 - 02:22 PM, said:
http://code.google.com/p/pkgcreator/
David J, on 12 November 2011 - 02:29 PM, said:
#5
Posted 12 November 2011 - 05:49 PM
I can help test installers as I have VM's for rhels, suse, Ubuntu, and Solaris. I just don't know how to package for Linux. Guess I should learn since I know how to package for windows. lol
#6
Posted 12 November 2011 - 06:41 PM
#7
Posted 12 November 2011 - 08:15 PM
David J, on 12 November 2011 - 06:41 PM, said:
I've been working on and off on building up a .deb package build system for GCS for a while now. Between real life work and some GCS enhancement work recently, the .deb stuff was sort of back burnered for a bit, but I'm back on it now. I've already PM'ed Dankers about it, but busy as he is, he may not have seen my most recent message yet, and an earlier one on this was probably lost in the noise of the other conversation's main subject.
I'm a long time Linux kernel dev, so Linux is very familiar to me. But, when it comes to .deb packages, it is new territory for me and I'm having to learn as I go. As you mention, conceptually, building a .deb is fairly easy. Unfortunately due to the complexity of how GCS gets built, it is making the .deb process troublesome.
I'm running into an issue with one of GCS' self built libraries trying to find another of its self built libs. As the package tools are building packages, they try to build up the dependencies map for the package. It seems the internal search path that libExtensionSystem gets built with for searching for libAggregation has a "strangeness" to it. I'm guessing that the strangeness has been added for the sake of either Windoz or Mac OS/x, but for Linux it is probably a bug in the generation of libExtensionSystem.
I've been trying to chase down how to handle it, but no success so far. Still hammering away though.
#8
Posted 12 November 2011 - 09:46 PM
naiiawah, on 12 November 2011 - 08:15 PM, said:
being far less experienced, other than using Linux at work+home - I guess that's what caused my "simple" process of making .deb to end with a package containing several hundred MB's (or 1GB) - at least that's the problem I've never overcome - way too much got included because the automagic process thought it was needed.
#9
Posted 13 November 2011 - 02:18 AM
For whatever package type choose (.deb, .rpm, .tgz or even ebuild's
and despite the existing package converters it's always much more prone to fail.
As the OpenPilot project is a open source project, it can apply for a open source license from BitRock.
#10
Posted 13 November 2011 - 06:37 PM
#11
Posted 13 November 2011 - 06:46 PM
edit: and also has a nice "updater" feature witch will help create a GCS auto update.
#12
Posted 16 November 2011 - 06:39 PM
IceWind, on 13 November 2011 - 02:18 AM, said:
But I think that It conflicts with the goal of having whole project open so everyone can build all including installers and packages.



Norway
Portugal
New Zealand
United States
United Kingdom
Ireland
Australia
Ukraine







